Learn more about these different git repos.
Other Git URLs
It seems when trying to update an aarch64 machine from Fedora 31 to the current rawhide, there is an error due to the updates-modular repository, which as far as I know shouldn't be applicable for rawhide:
dnf system-upgrade download --refresh --releasever=rawhide
Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y Fedora Modular rawhide - aarch64 246 kB/s | 118 kB 00:00 Fedora Modular rawhide - aarch64 - Updates 105 kB/s | 57 kB 00:0
Errors during downloading metadata for repository 'updates-modular': - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-frawhide&arch=aarch64 (IP: 8.43.85.67) - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-frawhide&arch=aarch64 (IP: 8.43.85.73) - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-frawhide&arch=aarch64 (IP: 152.19.134.142) Error: Failed to download metadata for repo 'updates-modular': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-frawhide&arch=aarch64 (IP: 8.43.85.73)
This is not aarch64 specific. All stable to rawhide upgrades will hit this.
You should be able to disable fedora-modular, fedora-updates-modular and enable rawhide-modular.
It might be nice if we make mirrormanager redirect things here like we do for updates/updates-testing to avoid problems...
@adrian thoughts ^
Already worked around the issue by disabling the fedora-updates-modular repo, however I've already branched some different machines and I didn't hit the issue (unless it's a recent bug).
@adrian can we make 'alias' entries in mirrormanager from updates-released-modular and updates-testing-modular to rawhide-modular?
I would say the repository redirects exist. At least looking today at the database:
718 | updates-released-modular-f33 | rawhide-modular 719 | updates-testing-modular-f33 | rawhide-modular 720 | updates-released-modular-debug-f33 | rawhide-modular-debug 721 | updates-testing-modular-debug-f33 | rawhide-modular-debug 722 | updates-testing-modular-source-f33 | rawhide-modular-source 723 | updates-released-modular-source-f33 | rawhide-modular-source
The strange thing about the error message is updates-released-modular-frawhide. If it would be f33 it would work, but frawhide is not something we ever had. It is something we can add, but not sure if this is actually a correct repository name we need to handle?
updates-released-modular-frawhide
f33
frawhide
Yeah, this is due to the 'repo=updates-released-modular-f$releasever' in the repo file.
We have also 'repo=updates-released-f$releasever' for updates? How is that one handled?
I guess ideally we would nuke the 'f' from all these so we could have 'rawhide' or the number, but we would likely have to keep backward compat for a long time. ;(
I was just about to write, not at all, but had a closer look at the repository redirect table. If I actually scroll up I see that a redirect for frawhide exists. It has just been entered into the database a very long time ago.
I just added the redirects with frawhide also for the modular repositories:
insert into repository_redirect (from_repo , to_repo) values ('updates-released-modular-frawhide','rawhide-modular'); insert into repository_redirect (from_repo , to_repo) values ('updates-testing-modular-frawhide','rawhide-modular'); insert into repository_redirect (from_repo , to_repo) values ('updates-released-modular-debug-frawhide','rawhide-modular-debug'); insert into repository_redirect (from_repo , to_repo) values ('updates-testing-modular-debug-frawhide','rawhide-modular-debug'); insert into repository_redirect (from_repo , to_repo) values ('updates-testing-modular-source-frawhide','rawhide-modular-source'); insert into repository_redirect (from_repo , to_repo) values ('updates-released-modular-source-frawhide','rawhide-modular-source');
Should be live in about an hour. Ticket can be closed.
Thanks!
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.