I’ve been trying to upgrade from Fedora 40 do Fedora 41 for the last 3 days running
sudo dnf5 -y --releasever 41 system-upgrade download
and a few packages seem to be missing from all mirrors.
Examples:
paps-0.8.0-10.fc41.x86_64.rpm
python3-rpm-4.19.92-6.fc41.x86_64.rpm
rpm-plugin-ima-0:4.19.92-6.fc41.x86_64
I upgraded Fedora many times in the past and it’s the first time I have such issues. Is there some problem with package propagation among mirrors or what?
Try upgrading with DNF4 and check this if the issue persists:
dnf repolist; cat /etc/dnf/dnf.conf
I don’t have dnf, only dnf5.
$ dnf5 repolist
repo id repo name
copr:copr.fedorainfracloud.org:zeno:scrcpy Copr repo for scrcpy owned by zeno
fedora Fedora 40 - x86_64
fedora-cisco-openh264 Fedora 40 openh264 (From Cisco) - x86_64
insync insync repo
network_im_signal Signal Messaging Devel Project (Fedora_37)
rpmfusion-free RPM Fusion for Fedora 40 - Free
rpmfusion-free-updates RPM Fusion for Fedora 40 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 40 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 40 - Nonfree - Updates
rpmsphere RPM Sphere - Basearch
rpmsphere-noarch RPM Sphere - Noarch
teams teams
teamviewer TeamViewer - x86_64
updates Fedora 40 - x86_64 - Updates
$ cat /etc/dnf/dnf.conf
[main]
gpgcheck=True
installonly_limit=3
clean_requirements_on_remove=True
#best=False
skip_if_unavailable=True
I see no technical reason that stops you from installing DNF4 and using it to upgrade to Fedora 41.
Do you want to say it’s a known fact that there are problems upgrading with dnf5?
Dodano dnf5
You are putting the cart before the horse by using DNF5 before upgrading to Fedora 41.
DNF5 feels quite edgy and unpolished, so I would not be surprised if it’s the cause of the problem.
BTW, today I upgraded a testing VM to Fedora 41 using DNF4 without any issues.
Folks, there is no Fedora 41 yet. It’s a beta! And it’s called a beta for a reason. Also, the official way to upgrade from F40 is using dnf4 since dnf5 was never officially supported as a replacement of dnf4 in F40.
Note that versions of dnf5 in F40 and F41 (beta) are different, and so will be your experience.
These package have been updated and are now
python3-rpm.x86_64 4.19.94-1.fc41 fedora
rpm-plugin-ima.x86_64 4.19.94-1.fc41 fedora
paps.x86_64 0.8.0-11.fc41 fedora
The issues could be that you have packages which did not come from the fedora or rpmfusion repositories. If such packages causes version conflicts, it doesn’t matter if you use dnf4 or dnf5.
Also, sometimes the repository mirrors are in a not ready state, for example if they are in the middle of downloading packages from the fedora master repository. In that case, the issue may resolve itself a couple of hours later.
If you still encounter issues, you can also try the other supported way of upgrading to new major releases, including beta releases, via GNOME Software (supposing you’re using Workstation edition).
For that you would have to enable upgrading to pre-release versions via GNOME Software, by running the command gsettings set org.gnome.software show-upgrade-prerelease true[1]. Afterwords GNOME Software should propose upgrading to F41.
As always, system backups are recommended, and even more so before pre-release upgrades.
You might want to run the reverse command after upgrading to F41, so that you won’t get unwanted future upgrades. There were reports stating that pre-beta releases have also been proposed. ↩︎
After installing dnf and using it for an upgrade instead of dnf5 everything went smooth as always. Seems like a bug with dnf5. Interesting what this might be.
I think before downloading phase there is a phase when dnf resolves dependencies and there were no conflicts detected.
I know that’s why I’ve been trying for 3 consecutive days…
In the end I installed dnf and used it for an upgrade with no problems.
What is GNOME? (just kidding)
Formally yes, in practice beta for me ends about 2 months after branching 