On Wed, 10 Oct 2007 14:02:19 +0200, Till Maas wrote: > On Mi Oktober 10 2007, Michael Schwendt wrote: > > Revisiting the annoying "Metadata file does not match checksum" problem, > > > since it just came back here like this: > > The cached repomd.xml file is out-of-date from September 19th, and all > > the mirrors offer much newer repodata from Oct 8th. The mirrors are > > not to blame here, since Yum does not consider downloading a fresh copy. > > Instead, it seems it tries to fetch metadata files which match the old > > repomd index: > > > Is this observation right? > > I always experienced this with any Fedora Release I used (4-7) and imho your > observation is right. For me setting the metadata_expire high or just do > a "yum clean all" when this happens. $ grep meta /etc/yum.conf metadata_expire=1800 That's half an hour. The default I assume. Still, with mirrorlist enabled, it leads to this ugly situation, where Yum somehow relied on a repomd.xml file that was older than what 99% (?) of the mirrors offered. Without skimming over the source code, it smells much like if the cachecookie is recent enough, Yum will not retry loading the tiny repomd.xml and won't recover from the metadata checksum mismatch deadlock automatically. And 1800 seconds later it can run into the same problem again. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
