Yum Update - Metadata does not match checksum [Solved]
Ralf Corsepius
rc040203 at freenet.de
Tue Apr 13 03:52:16 UTC 2010
On 04/13/2010 04:53 AM, david walcroft wrote:
> On 04/12/2010 09:18 PM, Michael Schwendt wrote:
>> On Mon, 12 Apr 2010 07:45:26 +0200, Melanie wrote:
>>
>>> I found a lot of threads, that my ethernet controller makes problems. I
>>> use the Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express
>>> Gigabit Ethernet controller (rev 02). I read that for this card the
>>> wrong driver is used: R8169 instead of R8168.
>>
>> It's the same combination here, running without problems (albeit running in
>> a 100Mb/s speed network):
I don't think the NIC is the cause of this kind of issues.
> I'm getting the same problem with 'metadata'
So do I.
From a couple of minutes ago:
...
updates
| 4.4 kB 00:00
http://fedora.intergenia.de/updates/12/i386/repodata/repomd.xml: [Errno
-1] repomd.xml does not match metalink for updates
Trying other mirror.
...
> '[Errno -1] repomd.xml does not match metalink for updates'
I just compared the repomd.xml of one of the mirrors having been
reported as "does not match" against that yum put into its yum cache:
# lftp -c get
http://fedora.intergenia.de/updates/12/i386/repodata/repomd.xml
# cmp repomd.xml /var/cache/yum/fedora/12/i386/updates/repomd.xml
repomd.xml /var/cache/yum/fedora/12/i386/updates/repomd.xml differ: byte
138, line 2
Checking the contents of both files tells "intergenia's repomd.xml" is
older than that in yum's cache:
repomd.xml: <timestamp>1270862208</timestamp>
/var/cache/yum/fedora/12/i386/updates/repomd.xml:
<timestamp>1271090290</timestamp>
=> repos are out of sync, mirrormanager is not working correctly.
Ralf
More information about the users
mailing list