3:33 a.m.
Hi,
since some days I get absolutely no updates.
Under bodhi I can see (just a simple example)
gstreamer-plugins-base-0.10.19-2.fc9 on my system there is
[choeger@choeger6 svn]$ rpm -q gstreamer-plugins-base
gstreamer-plugins-base-0.10.19-1.fc9.i386
and yum says: no packages found.
I assume that goes for a lot of packages (including yum, gedit and
others I've had a look at).
What went wrong?
regards
christoph
4:32 a.m.
On Fri, 30 May 2008 10:33:43 +0200, Christoph Höger wrote:
Hi,
Wrong list? You seem to refer to F9 => fedora-list not
fedora-devel-list.
since some days I get absolutely no updates.
Are they available on your favourite mirror already?
Or do you use the mirrorlist?
Under bodhi I can see (just a simple example)
gstreamer-plugins-base-0.10.19-2.fc9
That's a very recent update, which takes time to travel to all mirrors.
and yum says: no packages found.
I assume that goes for a lot of packages (including yum, gedit and
others I've had a look at).
What went wrong?
"yum clean metadata", then try again. Alternatively, disable
mirrorlist and pick a nearby mirror, which is up-to-date often
and sooner than arbitrary mirrors on mirrorlist.
--
Fedora release 8 (Werewolf) - Linux 2.6.23.15-137.fc8
loadavg: 1.64 1.27 1.16
1:10 p.m.
New subject: no updates?no updates
Am Freitag, den 30.05.2008, 11:32 +0200 schrieb Michael Schwendt:
On Fri, 30 May 2008 10:33:43 +0200, Christoph Höger wrote:
> Hi,
Wrong list? You seem to refer to F9 => fedora-list not
fedora-devel-list.
Ah sorry, evolutions autocompletion got me, "fedora" was resolved to
fedora-devel. I should have a look at that feature.
> since some days I get absolutely no updates.
Are they available on your favourite mirror already?
Or do you use the mirrorlist?
That was the mirrorlist.
> Under bodhi I can see (just a simple example)
> gstreamer-plugins-base-0.10.19-2.fc9
That's a very recent update, which takes time to travel to all mirrors.
> and yum says: no packages found.
>
> I assume that goes for a lot of packages (including yum, gedit and
> others I've had a look at).
>
> What went wrong?
"yum clean metadata", then try again. Alternatively, disable
mirrorlist and pick a nearby mirror, which is up-to-date often
and sooner than arbitrary mirrors on mirrorlist.
--
Fedora release 8 (Werewolf) - Linux 2.6.23.15-137.fc8
loadavg: 1.64 1.27 1.16
yum clean metadata and _then_ yum clean all did the trick. I have no
idea why yum clean all did not work before.
Thank you anyway!
1:33 p.m.
New subject: no updates?no updates
On Fri, 30 May 2008 20:10:24 +0200, Christoph Höger wrote:
> "yum clean metadata", then try again. Alternatively,
disable
> mirrorlist and pick a nearby mirror, which is up-to-date often
> and sooner than arbitrary mirrors on mirrorlist.
yum clean metadata and _then_ yum clean all did the trick. I have no
idea why yum clean all did not work before.
Coincidence. :)
"clean all" includes "clean metadata" (see "man yum"), but
is not
needed. It is enough to purge metadata and retry till mirrorlist
points you to an up-to-date mirror.
You just deleted all downloaded/cached packages instead of just the
metadata files.
6:13 p.m.
On Fri, 2008-05-30 at 11:32 +0200, Michael Schwendt wrote:
On Fri, 30 May 2008 10:33:43 +0200, Christoph Höger wrote:
> Hi,
Wrong list? You seem to refer to F9 => fedora-list not
fedora-devel-list.
> since some days I get absolutely no updates.
Are they available on your favourite mirror already?
Or do you use the mirrorlist?
I've had this same problem a couple of times. You'll see updates coming
in in email to fedora-test-list and then after a couple of days you'll
notice that the updates never happened.
If I then yum clean all the updates work as soon as I run yum update
manually.
I think there might be a bug here, but haven't got any idea how to test
for it, and haven't got around to reporting it either.
R.
--
"It's a fine line between denial and faith.
It's much better on my side"
2:14 a.m.
On Sun, 01 Jun 2008 09:13:15 +1000, Rodd Clarkson wrote:
On Fri, 2008-05-30 at 11:32 +0200, Michael Schwendt wrote:
> On Fri, 30 May 2008 10:33:43 +0200, Christoph Höger wrote:
>
> > Hi,
>
> Wrong list? You seem to refer to F9 => fedora-list not
> fedora-devel-list.
>
> > since some days I get absolutely no updates.
>
> Are they available on your favourite mirror already?
> Or do you use the mirrorlist?
I've had this same problem a couple of times. You'll see updates coming
in in email to fedora-test-list and then after a couple of days you'll
notice that the updates never happened.
If I then yum clean all the updates work as soon as I run yum update
manually.
I think there might be a bug here, but haven't got any idea how to test
for it, and haven't got around to reporting it either.
You can test for it by examining the cached metadata files below
/var/cache/yum/updates. Start with the timestamp on "cachecookie". Only if
old enough, Yum loads new metadata. [The default is 1800 seconds in
yum.conf's metadata_expire= value.] Compare timestamp of "repomd.xml" with
the mirror that is assigned to you (file "mirrorlist.txt". Recent Yum
versions ignore mirrors that offer repomd.xml files which are older than
what you've got in your cache. This way you can find mirrors which don't
sync daily.
--
Fedora release 8 (Werewolf) - Linux 2.6.23.15-137.fc8
loadavg: 1.21 1.17 0.74
11:34 p.m.
On Sun, 2008-06-01 at 09:14 +0200, Michael Schwendt wrote:
You can test for it by examining the cached metadata files below
/var/cache/yum/updates. Start with the timestamp on "cachecookie". Only if
old enough, Yum loads new metadata. [The default is 1800 seconds in
yum.conf's metadata_expire= value.] Compare timestamp of "repomd.xml" with
the mirror that is assigned to you (file "mirrorlist.txt". Recent Yum
versions ignore mirrors that offer repomd.xml files which are older than
what you've got in your cache. This way you can find mirrors which don't
sync daily.
Right, so I see this:
in repomd.xml
<?xml version="1.0" ?><repomd
xmlns="http://linux.duke.edu/metadata/repo">
In mirrorlist.txt
# repo = updates-released-f9 arch = i386 country = AU
http://mirror.optus.net/fedora/linux/updates/9/i386
http://ftp.iinet.net.au/pub/fedora/linux/updates/9/i386
http://mirror.3fl.net.au/pub/fedora/linux/updates/9/i386
http://mirror.internode.on.net/pub/fedora/linux/updates/9/i386
http://mirror.aarnet.edu.au/pub/fedora/linux/updates/9/i386
http://ringtail.its.monash.edu.au/pub/fedora/linux/updates/9/i386
I'm not seeing linux.duke.edu in here. Should I?
R.
--
Fedora release 8 (Werewolf) - Linux 2.6.23.15-137.fc8
loadavg: 1.21 1.17 0.74
--
"It's a fine line between denial and faith.
It's much better on my side"
4:05 a.m.
On Tue, 03 Jun 2008 14:34:13 +1000, Rodd Clarkson wrote:
On Sun, 2008-06-01 at 09:14 +0200, Michael Schwendt wrote:
> You can test for it by examining the cached metadata files below
> /var/cache/yum/updates. Start with the timestamp on "cachecookie". Only
if
> old enough, Yum loads new metadata. [The default is 1800 seconds in
> yum.conf's metadata_expire= value.] Compare timestamp of "repomd.xml"
with
> the mirror that is assigned to you (file "mirrorlist.txt". Recent Yum
> versions ignore mirrors that offer repomd.xml files which are older than
> what you've got in your cache. This way you can find mirrors which don't
> sync daily.
Right, so I see this:
in repomd.xml
<?xml version="1.0" ?><repomd
xmlns="http://linux.duke.edu/metadata/repo">
In mirrorlist.txt
# repo = updates-released-f9 arch = i386 country = AU
http://mirror.optus.net/fedora/linux/updates/9/i386
http://ftp.iinet.net.au/pub/fedora/linux/updates/9/i386
http://mirror.3fl.net.au/pub/fedora/linux/updates/9/i386
http://mirror.internode.on.net/pub/fedora/linux/updates/9/i386
http://mirror.aarnet.edu.au/pub/fedora/linux/updates/9/i386
http://ringtail.its.monash.edu.au/pub/fedora/linux/updates/9/i386
I'm not seeing linux.duke.edu in here. Should I?
No, because it's only an XML namespace parameter in the repomd.xml
header pointing to the DTD file. Every repomd.xml file contains it at
the beginning.
5805
days inactive
5809
days old
7 comments
3 participants
participants (3)
-
Christoph Höger -
Michael Schwendt -
Rodd Clarkson