Bug 1575433
| Summary: | dnf - Unable to detect release version | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matt Daveson <reportbug> |
| Component: | dnf | Assignee: | Jaroslav Mracek <jmracek> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 29 | CC: | blaise, dmach, jmracek, ncoghlan, packaging-team-maint, reportbug, rpm-software-management, sallyahaj, tkriviradev, vmukhame |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | Flags: | ncoghlan:
needinfo+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-03 18:17:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Matt Daveson
2018-05-06 23:24:15 UTC
I couldn't update or install as well any package using 'dnf' in "Fedora 28 Standard Base Cloud HVM AMIs" on AWS, I get this message: "Unable to detect release version (use '--releasever' to specify release version) Error: Failed to synchronize cache for repo 'updates'" By the way, I could use --releasever with the command which works as the following sudo dnf --releasever 28 update This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. Please can you provide an output from command ``dnf repoquery fedora-release``. Probably command "dnf reinstall fedora-release" could help. Without additional information we cannot do much. I confirm on fresh installed Fedora 32 Lenovo T450 This is the only way to dnf update currently. sudo dnf update -y --releasever 32 uname -a Linux localhost.localdomain 5.6.6-300.fc32.x86_64 #1 SMP Tue Apr 21 13:44:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux dnf repoquery fedora-release Unable to detect release version (use '--releasever' to specify release version) Fedora $releasever openh264 (From Cisco) - x86_64 12 kB/s | 63 kB 00:05 Errors during downloading metadata for repository 'fedora-cisco-openh264': - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=x86_64 (IP: 2610:28:3090:3001:dead:beef:cafe:fed3) Error: Failed to download metadata for repo 'fedora-cisco-openh264': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=x86_64 (IP: 2610:28:3090:3001:dead:beef:cafe:fed3) Fedora Modular $releasever - x86_64 12 kB/s | 63 kB 00:05 Errors during downloading metadata for repository 'fedora-modular': - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-$releasever&arch=x86_64 (IP: 2610:28:3090:3001:dead:beef:cafe:fed3) Error: Failed to download metadata for repo 'fedora-modular': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-$releasever&arch=x86_64 (IP: 2610:28:3090:3001:dead:beef:cafe:fed3) I ran into this problem after updating from Fedora 31 to Fedora 32 (and from there to Fedora 34).
The "fedora-release" package somehow seemed to be missing, and this resolved it:
sudo dnf install fedora-release --releasever=34
Thank you @ncoghlan , this helped me out of a tight spot. I think I mangled the cache when I mounted an additional filesystem under /var . `Error: Could not set cachedir: [Errno 2] No such file or directory: '/var/tmp/dnf-blaise-u5apbcuc'` This comment was flagged a spam, view the edit history to see the original text if required. |