Red Hat Bugzilla – Bug 498720
Packaging bug: metalink
Last modified: 2013-01-10 00:11:53 EST
Description of problem:
/etc/yum.repos.d/fedora*.repo files use "metalink" mirrorlist URLs.
Such URLs are unreadable by FC10's yum, nevertheless
the package fedora-release-10.92-1.noarch.rpm
installs without complaints on FC10.
=> Packaging bug: missing "Requires: ... > xxx"
(likely some version of yum-metadata-parser)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. On FC10: rpm -U fedora-release-10.92-1.noarch.rpm
2. yum update
yum complains about invalid mirrorlists and aborts.
fedora-release being non-installable on systems with insufficent yum-metadata-parsers
The metalink-URL breaks the traditional approach to distro upgrading (Manually upgrade fedora-release, then run yum upgrade).
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Get the yum from updates-testing in Fed-10.
I'm not sure there's a point in keeping this open.
(In reply to comment #3)
> I'm not sure there's a point in keeping this open.
You may close this bug when you released a bug-fixed package in F-10
Until then this bug is still present.
Besides this, this bug should have been addressed long before F11 had been released, unfortunately this package's maintainer (Jesse Keating) preferred to ignore it.
*** Bug 504941 has been marked as a duplicate of this bug. ***
a really bad timing :-(
fc11 release date was 2009-06-10
'yum update' before the upgrade == yum 3.2.21-2.fc10
yum 3.2.23-3.fc10 in updates-testing is from 2009-05-23
yum 3.2.21-2.fc10 in fedora-updates is from 2009-02-04
imho it would be no bad idea if the working yum package would be as soon as possible in fedora-updates before the release date.
I ignored it because the yum folks said they would be putting out a yum update that would fix it. We're trying to get that yum moved over, however something in the F12 content has made our rawhide composes take longer than a day which is making it difficult to get any update pushes out.
I ran into this one trying to yum upgrade one of my F10 boxes to F11.
Workaround appears to be described here:
I've added a link to this bug and to the workaround to: