At 7:42 AM -0300 6/27/06, Clodoaldo Pinto wrote: >Fedora Core 5 > ># yum provides rpmbuild >Reading repository metadata in from local files >Importing additional filelist information >filelists.xml.gz 100% |=========================| 2.3 MB 00:45 >core : ################################################## 2207/2207 >Added 2207 new packages, deleted 0 old in 28.47 seconds >filelists.xml.gz 100% |=========================| 4.4 MB 01:14 >updates : ################################################## 1339/1339 >Added 1339 new packages, deleted 0 old in 56.90 seconds >filelists.xml.gz 100% |=========================| 2.8 MB 01:08 >http://mirror.linux.duke.edu/pub/fedora/linux/extras/5/i386/repodata/filelists. >xml.gz: >[Errno -1] Metadata file does not match checksum >Trying other mirror. >filelists.xml.gz 100% |=========================| 2.8 MB 00:47 >http://download.fedora.redhat.com/pub/fedora/linux/extras/5/i386/repodata/filel >ists.xml.gz: >[Errno -1] Metadata file does not match checksum >Trying other mirror. If you wait the problem will go away. It is common for the various mirrors to be at different dates as updates occur and the mirrors gradually get them, so this sort of thing can happen for several mirrors in a row. If it happens for all the mirrors, it is often because -- in the half-hour that yum considers its cache valid -- an update has been sucked up by the (rest of) the mirrors. Waiting for yum will work, as will "yum clean metadata" and trying again. I have written a yum plugin, stablemirror, that tries to prevent such issues by always checking that a mirror's metadata matches what yum is expecting: <http://georgeanelson.com/stablemirror.htm> ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/>
