Todays updates error

[wvn]

Was it f9 or f10 when that security compromise appeared? Not again.

[bob]

"Paranoia strikes deep
Into your life it will creep
It starts when you're always afraid
You step out of line
The man come
And take you away"

(apologies to Buffalo Springfield)

[JN4OldSchool]

Stop, hey, what's that sound
Dont look now, yum is going down...

[SeRi@lDiE]

Add me to the list... The F11 repos are so broken that is not even funny!

[leftoflexo]

ive had the same problem with the updates:

Errors were encountered while downloading packages.
grubby-6.0.87-1.fc11.i586: failure: grubby-6.0.87-1.fc11.i586.rpm from updates: (256, 'No more mirrors to try.')
freedoom-0.6.4-1.fc11.noarch: failure: freedoom-0.6.4-1.fc11.noarch.rpm from updates: (256, 'No more mirrors to try.')
farsight2-0.0.12-1.fc11.i586: failure: farsight2-0.0.12-1.fc11.i586.rpm from updates: (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: (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: (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: (256, 'No more mirrors to try.')
gdb-6.8.50.20090302-33.fc11.i586: failure: gdb-6.8.50.20090302-33.fc11.i586.rpm from updates: (256, 'No more mirrors to try.')
freedoom-freedm-0.6.4-1.fc11.noarch: failure: freedoom-freedm-0.6.4-1.fc11.noarc...


currently running "yum update" and got this..

[root@chaos lefto]# yum clean all
Loaded plugins: protectbase, refresh-packagekit
Cleaning up Everything
[root@chaos lefto]# yum update
Loaded plugins: protectbase, refresh-packagekit
adobe-linux-i386 | 951 B 00:00
adobe-linux-i386/primary | 11 kB 00:00
adobe-linux-i386 17/17
fedora/metalink | 28 kB 00:00
fedora | 3.8 kB 00:00
fedora/primary_db 65% [=========- ] 3.8 kB/s | 5.5 MB 13:04 ETA


so at least that is working somewhat. im pretty sure its talking to the same server as the update manager
but the speed is very very slow, yum has been terribly slow for three days where i am and i have a 1.5 mbps connection. 3.8k has been the fastest its gone all week, it normally hovers around 1.5 or so.

[zorgoth]

I have the same problem. I have had it for about 15 hours I think. It is the first 6 alphabetical packages again.

[itsjustarumour]

+ 1 for this issue. The update packages I'm trying to download are pretty much the same as WVN mentioned in their post. I've been trying for about 4 hours.

[leftoflexo]

yup it asked it if it was ok to install everything and i typed yes, now its giving me mirror errors again. how strange since it looked like it was actually downloading what with the download speed and progress indicator

[cschol2112]

Same problem here. It has been broken since the update notification popped up last night. I get 404 on pretty much every packet it tries to update.

[SlowJet]

http://mirrors.kernel.org/fedora/upd...i386/repodata/

Until repodata changes, it's all smoke and mirrors.
All you need to do is check two or three local mirrors before updating.
http://fedoraproject.org
Get Fedora
see all mirrors

SJ

[jerkface]

At the risk of sound totally paranoid, this could also be a sign that one of the mirrors has a security problem. I think I will hold off on updating until there is word from someone in the Fedora Project or at least the bugzilla gets closed.

Damn, should've known it was another security issue.

[Pincha]

I have the same problem, but to fix it (for this update) i use this

yum --exclude="alsa-plugins-pulseaudio dhclient farsight2 gdb grubby gstreamer-plugins-good hugs98" update --skip-broken

[zorgoth]

What's with the alphabetical thing anyway?

[ilja]

What's with the alphabetical thing anyway?

Most probably the server update their repositories in an alphabetical order. And something happened to the orginial server while they synchronised the first six. This would be my guess.

[Gödel]

I was able to update ok today, I have yum-presto installed, so maybe the deltarpms aren't affected by the issues everyone else is seeing

On one x86_64 install of F11 I had to do the following:

yum clean metadata

Then I ran 'yum update' and while the primary_db was being downloaded (very slowly) hit ctrl-c (just once), after a short pause the update resumed much quicker, and completed without error