Bug 790530
Summary: | yum install fails - No repomd file | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | satellitgo |
Component: | distribution | Assignee: | Kevin Fenzi <kevin> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | awilliam, dennis, ffesti, james.antill, maxamillion, pmatilai, satellitgo, tim.lauridsen, zpavlas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-15 16:49:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 752648 |
Description
satellitgo
2012-02-14 18:55:46 UTC
https://mirrors.fedoraproject.org/metalink?repo=fedora-17&arch=i386 The application you chose ("") could not be found. Check the file name or choose another application. This looks like a releng issue, not yum: # repo=fedora-17, arch=i386 is missing from the metalink stuff, if you look through the error output (click on the link above and open it in gedit). Assigning to releng people. Proposing as Alpha blocker, as this probably prevents updates working on i386 - "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops". Note this doesn't need a package update, so it's not a blocker that affects spinning. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Seems to also have been reported through trac, as https://fedorahosted.org/fedora-infrastructure/ticket/3142 . this is fixed now. sorry for the trouble. ;( There's a mirrormanager bug that was exposed, and will hopefully be fixed now. |