Is any one else failing dnf system-upgrading to Fedora 44 Beta due to "LibRaw" package?

Ask Fedora
1

I’m on Fedora 43 KDE and want to try system-upgrading to Fedora 44 Beta.

command used:

sudo dnf system-upgrade download –-releasever=44

I’m having these types of hang ups (Note on the real run, there were many more mirrors tried but I shortened the below for brevity):

[ 189/4536] NetworkManager-wifi-1:1.56.0-1.fc44.x86_64                                                                                                        100% | 179.3 KiB/s | 136.5 KiB |  00m01s
[ 190/4536] NetworkManager-wwan-1:1.56.0-1.fc44.x86_64                                                                                                        100% |  51.2 KiB/s |  58.6 KiB |  00m01s
[ 191/4536] LibRaw-0:0.21.5-3.fc44.x86_64                                                                                                                     100% |  49.0   B/s | 236.0   B |  00m05s

Status code: 404 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/development/44/Everything/x86_64/os/Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm (IP: 54.230.21.6) - https://d2lzkl7pfhq
Status code: 404 for https://dl.fedoraproject.org/pub/fedora/linux/development/44/Everything/x86_64/os/Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm (IP: 38.145.32.23) - https://dl.fedoraproject.or
Status code: 404 for https://dl.fedoraproject.org/pub/fedora/linux/development/44/Everything/x86_64/os/Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm (IP: 38.145.32.23) - https://dl.fedoraproject.or
Curl error (7): Could not connect to server for https://ftp.uni-stuttgart.de/fedora/development/44/Everything/x86_64/os/Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm [Failed to connect to ftp.uni-s
Curl error (7): Could not connect to server for http://ftp.uni-stuttgart.de/fedora/development/44/Everything/x86_64/os/Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm [Failed to connect to ftp.uni-st

No more mirrors to try - All mirrors were already tried without success
Not finished - interrupted by error: Cannot download Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm: All mirrors were tried
[ 193/4536] kernel-modules-core-0:6.19.6-300.fc44.x86_64                                                                                                       22% |   3.4 MiB/s |  16.5 MiB |  00m05s
Not finished - interrupted by error: Cannot download Packages/l/LibRaw-0.21.5-3.fc44.x86_64.rpm: All mirrors were tried

When I look in the dl.fedoraproject.org “development” repo for “l” packages for 44 directly with a browser I see the obvious problem, the browser shows the LibRaw rpm is really:

LibRaw-0.22.0-1.fc44.x86_64.rpm 2026-03-03 21:32 484K

So dnf system-upgrade to “44” is trying to get LibRaw version 0.21.5-3 but it really should be 0.22.0-1

Is this a case where the repo server simply has stale xml repodata files and trying later would probably fix that?

3

What exact commands are you using in your attempt to do the upgrade.?

You should follow this doc, and the very first command to run before running the system-upgrade step is sudo dnf upgrade --refresh to ensure the current version is fully updated (and also ensures your dnf metadata cache is updated as well).

Then when you run the command in step 2 change it to read sudo dnf system-upgrade download --releasever=44 --refresh since that will also refresh the metadatacache for f44 and it should pull in the proper packages.

1 Like
4

I quoted the command right at the top of the post (after “command used:”)

It was fully updated so “dnf upgrade –refresh” was in effect

Then when you run the command in step 2 change it to read sudo dnf system-upgrade download --releasever=44 --refresh since that will also refresh the metadatacache for f44 and it should pull in the proper packages.

Why doesn’t he official document include the --refresh on the 2nd command if it’s necessary? I would think the local cache would have to pull in everything for 44 since it wouldn’t have f44 metadata by definition

1 Like
6

There are issues with 44 have some older versions then 43 because of human error.
Not sure if this is one of them or not.

It is worthy reporting this as a bug in the Fedora bug tracker.

7

It is not required for everyone, though if someone has previously reached a mirror that has stale metadata it may remain and interfere with updates from mirrors with current content.

8

Re-ran with the --refresh on the system-upgrade download, this now worked. But since it was about a day since I got back to this since the first run with the failing LibRaw, I don’t know if it was just due to dnf5 picking a different mirror, the mirror being upgraded/changed or that the refresh fixed it.

thanks

2 Likes