Red Hat Bugzilla – Bug 510898
Mirrors don't have all the packages/out of sync despite being returned by mirrormanager
Last modified: 2014-01-21 18:10:41 EST
Description of problem:
yum install gdb
on an almost fresh F11, the following kind of error message is displayed for every available mirror:
Error Downloading Packages:
gdb-188.8.131.5290302-33.fc11.i586: failure: gdb-184.108.40.20690302-33.fc11.i586.rpm from updates: (256, 'No more mirrors to try.')
And indeed, it turns out that only
gdb-220.127.116.1190302-32 (note the final digit)
is available on the repository.
Similar problems occur with many (perhaps all) other "updates" packages.
Version-Release number of selected component (if applicable):
"uname -a" returns
Linux localhost.localdomain 18.104.22.168-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009 i686 i686 i386 GNU/Linux
The yum version is 3.2.23
I believe it should be reproducible immediately on any installation of F11 by trying to install "gdb".
The error message above is is displayed and no package is installed.
The "gdb" package should be installed.
When I tried to update my F11 system, the first six updates (alphabetically) could not be found or were truncated -
# ls -l /var/cache/yum/updates/packages/
-rw-r--r--. 1 root root 9606 2009-07-12 10:41 alsa-plugins-pulseaudio-1.0.20-2.fc11.i586.rpm
-rw-r--r--. 1 root root 9606 2009-07-12 10:42 dhclient-4.1.0-22.fc11.i586.rpm
-rw-r--r--. 1 root root 9606 2009-07-12 10:43 farsight2-0.0.12-1.fc11.i586.rpm
-rw-r--r--. 1 root root 9606 2009-07-12 10:45 gdb-22.214.171.12490302-33.fc11.i586.rpm
-rw-r--r--. 1 root root 9606 2009-07-12 10:46 grubby-6.0.87-1.fc11.i586.rpm
-rw-r--r--. 1 root root 9606 2009-07-12 10:47 gstreamer-plugins-good-0.10.15-3.fc11.i586.rpm
( . . . )
Using the info from this post:
I was able to do a partial upgrade just now with:
sudo yum --exclude=[a-h]\* update --skip-broken
From the above, as well as some further attempts to install other modules, it seems that the correct versions of at least the following modules are missing from the updates repository:
Error Downloading Packages:
grubby-6.0.87-1.fc11.i586: failure: grubby-6.0.87-1.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
12:dhcp-4.1.0-22.fc11.i586: failure: dhcp-4.1.0-22.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
farsight2-0.0.12-1.fc11.i586: failure: farsight2-0.0.12-1.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
12:dhclient-4.1.0-22.fc11.i586: failure: dhclient-4.1.0-22.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
alsa-plugins-pulseaudio-1.0.20-2.fc11.i586: failure: alsa-plugins-pulseaudio-1.0.20-2.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
gstreamer-plugins-good-0.10.15-3.fc11.i586: failure: gstreamer-plugins-good-0.10.15-3.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
gdb-126.96.36.19990302-33.fc11.i586: failure: gdb-188.8.131.5290302-33.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
The versions I'm having problems with can all be found in updates-testing, not updates.
gdb and alsa-plugins-pulseaudio as well as all packages that were needed when I ran "yum update" on my installation seem to be available now and yum performs the installation/update as expected.
As far as I am concerned the problem has been solved.
This appears to be caused by a problem in our mirror manager infrastructure this weekend. It had lost its geolocation database and was giving out incorrect responses.
*** Bug 510959 has been marked as a duplicate of this bug. ***
*** Bug 510986 has been marked as a duplicate of this bug. ***
*** Bug 510992 has been marked as a duplicate of this bug. ***
I am stil seeing this issue. What to do? Wait for mirrors to get back in sync? Use a specific one? clean yum cache (already tried)?
*** Bug 510963 has been marked as a duplicate of this bug. ***
In answer to comment #10 - just wait - the mirror/infrastructure team is trying to sort out what went wrong.
Thx. I got all updates downloaded now, even though some mirrors reported 404 on alsa-plugins-pulseaudio.
This is closed?
Still fails for me:
---> Package alsa-plugins-jack.i586 0:1.0.20-2.fc11 set to be updated
---> Package alsa-plugins-pulseaudio.i586 0:1.0.20-2.fc11 set to be updated
---> Package gdb.i586 0:184.108.40.20690302-33.fc11 set to be updated
Trying other mirror.
Some Mirror [mErrno 14] HTTP Error 404: Not Found
Trying other mirror.
Another Mirror [mErrno 14] HTTP Error 404: Not Found
Also, I "manually" looked for these packages at http://mirrors.fedoraproject.org/publiclist/Fedora/11/ and could not find any mirrors that have them.
Do these packages actually exist on a mirror somewhere? If so, maybe someone could post a link.
It's closed as a yum bug - It's still ongoing as a mirror issue.
Check the testing repos for those files.
Just as a clarification, this is NOT a yum issue. It is a infrastructure problem that the team is working on. More details at
Everyone be patient.
This is high time to reconsider wasteful policy of carrying on with two active streams of updates. If people want to see 250 Mb of KDE 4.3 in the near future, they should move their butts to Fedora 11 instead of suckling on Fedora 10.
This is not user's fault actually, but some developers just waste Redhat's bandwidth and do busy work updating older distros. I mean I don't mind security updates, which are far and few in between (historically 5-7%), but KDE 4.3.0...1...2...3...4... there goes 2 Gb in one release cycle. You can get Fedora 11 in the first place for less money. Sorry KDE, but same goes for openoffice.org and many other not so security critical apps.
Freeze Fedora 10 Already!!!!!!
Packagers should try to start developing in the freed time.
I would even block bug reports against old stuff.
A 6 month support cycle would render fedora non-viable for a great many users, including me. The extended support cycle widens fedora's relevance within the user base. I migrate systems as soon as I can, but I am still running 10 on a number of systems and will continue to do so for several months. Nothing I can do about it. I would NOT be able to use fedora at all if the support period were just 6 months, and I know a lot of people are in the same boat.
*** Bug 512018 has been marked as a duplicate of this bug. ***
I did not suggest to drop Fedora 10 on the floor and step over it.
Exploitable security issues should be fixed for as long as possible.
Like I said, this only accounts for 5-7% of updates.
It sound like you want new features and minor fixes delivered to you.
Current Fedora would do it for you too. RHEL would do it for
you for a few years.
Old Fedora feels the niche of lazy and cheap users. The value they
provide back to Red Hat is almost zero, but they cost same money.
The worst part actually comes at release +/- 1-month, when 4 (FOUR!) simultaneous builds of the same package occur! That's is a stress.
FYI, the infrastructure issue is not sorted out yet, almost one week later.
Sorry, I thought this link was posted here, but apparently not.
The issue is currently being tracked in the Infrastructure trac at https://fedorahosted.org/fedora-infrastructure/ticket/1531 - that's where all the latest updates are.
Alexei 'we' are losing people to Ubuntu - because people are pressured to upgrade Fedora too often. I got an email from a friend about a Linux installfest locally (Wellington, New Zealand), and Fedora is off the menu for newbies because it does not have a long germ stable version. Also since I am working from home now, and have a minimalist budget, I may have to switch myself.
People that go from Fedora -> Ubuntu and not from Fedora -> RHEL/CentOS aren't leaving because of the upgrade cycle.