You could remove the package python3-googleapis-common-protos-1.63.0-1.fc40.noarch
that is causing the update to fail. Do the update, then reinstall it.
Last metadata expiration check: 0:21:33 ago on Tue 23 Apr 2024 17:43:08 BST.
Dependencies resolved.
==========================================================================================================================================================================================
Package Architecture Version Repository Size
==========================================================================================================================================================================================
Installing:
python3-googleapis-common-protos noarch 1.63.0-1.fc40 fedora 227 k
Installing dependencies:
python3-protobuf x86_64 3.19.6-8.fc40 fedora 411 k
Transaction Summary
==========================================================================================================================================================================================
Install 2 Packages
Total download size: 638 k
Installed size: 2.6 M
Downloading Packages:
(1/2): python3-googleapis-common-protos-1.63.0-1.fc40.noarch.rpm 910 kB/s | 227 kB 00:00
(2/2): python3-protobuf-3.19.6-8.fc40.x86_64.rpm 1.4 MB/s | 411 kB 00:00
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 569 kB/s | 638 kB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : python3-protobuf-3.19.6-8.fc40.x86_64 1/2
Installing : python3-googleapis-common-protos-1.63.0-1.fc40.noarch 2/2
Running scriptlet: python3-googleapis-common-protos-1.63.0-1.fc40.noarch 2/2
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
User sessions running outdated binaries:
darkufo @ user manager service: systemd[24344]
No VM guests are running outdated hypervisor (qemu) binaries on this host.
Installed:
python3-googleapis-common-protos-1.63.0-1.fc40.noarch python3-protobuf-3.19.6-8.fc40.x86_64
Complete!
However when I then do a
sudo dnf5 upgrade --refresh -y
I get the same issue again
Repositories loaded.
Problem: package python3-googleapis-common-protos-1.63.0-1.fc40.noarch requires ((python3.12dist(protobuf) < 3.20 or python3.12dist(protobuf) > 3.20) with (python3.12dist(protobuf) < 3.20.1 or python3.12dist(protobuf) > 3.20.1) with (python3.12dist(protobuf) < 4.21.1 or python3.12dist(protobuf) > 4.21.1) with (python3.12dist(protobuf) < 4.21.2 or python3.12dist(protobuf) > 4.21.2) with (python3.12dist(protobuf) < 4.21.3 or python3.12dist(protobuf) > 4.21.3) with (python3.12dist(protobuf) < 4.21.4 or python3.12dist(protobuf) > 4.21.4) with (python3.12dist(protobuf) < 4.21.5 or python3.12dist(protobuf) > 4.21.5) with python3.12dist(protobuf) < 5~~dev0 with python3.12dist(protobuf) >= 3.19.5), but none of the providers can be installed
- cannot install both python3-protobuf-3.19.6-8.fc40.x86_64 and python3-protobuf-5.26.1-1.fc40.x86_64
- cannot install the best update candidate for package python3-protobuf-3.19.6-8.fc40.x86_64
- cannot install the best update candidate for package python3-googleapis-common-protos-1.63.0-1.fc40.noarch
This package appears to be coming from one of your third-party repositories, and seems to be the origin of the conflict. We are trying to work out all the compatibility issues to ship a current version of protobuf in Fedora 41, but there is no python3-protobuf-5.26.1 in Fedora 40 or even in Rawhide right now.
(I maintain python-googleapis-common-protos in Fedora, and I’m familiar with the protobuf package. If there is a problem in Fedora proper, I can fix it. I probably can’t do anything about what appears to be a conflicting third-party package.)
Note that dnf5 is not fully ready, but is more of a beta stage right now. Not all that works with dnf will work with dnf5 as yet. (dnf and dnf4 both use dnf-3 as the actual tool in use). Also note that dnf5 is not installed as yet by default even on f40.
$ ls -l /usr/bin/dnf*
lrwxrwxrwx. 1 root root 5 Mar 28 19:00 /usr/bin/dnf -> dnf-3
-rwxr-xr-x. 1 root root 2092 Mar 28 19:00 /usr/bin/dnf-3
lrwxrwxrwx. 1 root root 5 Mar 28 19:00 /usr/bin/dnf4 -> dnf-3