PDA

View Full Version : Fedora 8 - yumex - Metadata file does not match checksum



yeoheric
27th November 2007, 05:13 PM
Hi,

I have installed F8 Gnome from the Live CD (only from Live CD will it detect my wireless), everything worked like a charm until this afternoon I bailed out of yumex whicle it was installing some stuff.

Then whenever I start yumex it will:

Failure getting http://mirror.yandex.ru/fedora/linux/updates/8/i386/repodata/comps-f8.xml:
23:44:07 : --> [Errno -1] Metadata file does not match checksum
23:44:07 : Trying other mirror.
23:45:27 : Failure getting http://ftp.chg.ru/pub/Linux/fedora/linux/updates/8/i386/repodata/comps-f8.xml:
23:45:27 : --> [Errno -1] Metadata file does not match checksum
23:45:27 : Trying other mirror.
23:47:01 : Failure getting http://ftp.jaist.ac.jp/pub/Linux/Fedora/updates/8/i386/repodata/comps-f8.xml:
23:47:01 : --> [Errno -1] Metadata file does not match checksum
23:47:01 : Trying other mirror.
23:47:15 : Failure getting http://ftp.riken.jp/Linux/fedora/updates/8/i386/repodata/comps-f8.xml:
23:47:15 : --> [Errno -1] Metadata file does not match checksum
23:47:15 : Trying other mirror.

I tried yum clean metadata then yum clean all and then yum update. Still the same issue.

Please help. I mean what's the use of a GUI package manager if it dies on me for something so trivial?

Please help.

Eric

bob
27th November 2007, 05:31 PM
http://forums.fedoraforum.org/forum/showthread.php?t=171712 You Are Not Alone! :eek:

As info, I used the CLI 'yum update' which works fine, and there's an update for Yumex. I'll try again after that finishes up. Looks like some major updates in the works today.

coppertrail
27th November 2007, 05:47 PM
I'm getting the same thing with Yumex. I think it's a repo issue, the Redhat System updater popped up and indicated it couldn't get updates for my system and to check the network connection, which is/has been working fine.

bob
27th November 2007, 05:48 PM
Annnnddddd....no difference. :( after the yumex update. I'll keep playing but it's sure a glitch.

yeoheric
27th November 2007, 06:23 PM
Hmmm.....in the mean time.....I guess I am stuck with this or run back to Ubuntu. All those talk about being a polished and professional distro....seems like a bad joke.

bob
27th November 2007, 06:28 PM
This is not a normal problem. But you can certainly get things done with the CLI version which most of us prefer. Just open a terminal and sign in as root (su -), then type 'yum update' . For more info on yum, type 'man yum' or read up on it here: http://docs.fedoraproject.org/yum/en/

jbannon
27th November 2007, 06:39 PM
Servers are probably screwed again. The last time this happened it cleared itself within a day or two.

bob
27th November 2007, 06:54 PM
Well, if that's the case, why is yum working but not pirut, pup or yumex?

Seve
27th November 2007, 07:04 PM
Hello:
Is this problem with the newest version of Yumex 2.0.3 ?

In the past when I have had a similar issue with Yumex?

I usually do [ymmv]

yum clean all
yum remove yumex
yum clean all
yum -y install yumex
yum clean all
yumex

Seve

jbannon
27th November 2007, 07:13 PM
Well, if that's the case, why is yum working but not pirut, pup or yumex?
I'm only saying that's what happened the last time this was a problem. It seemed to clear up once the servers had settled down. I usually notice it when the Language setting app doesn't work properly and you have to edit /etc/sysconfig/i18n by hand.

vodamaxe
27th November 2007, 09:12 PM
as the error message says
comps-f8.xml:
23:47:15 : --> [Errno -1] Metadata file does not match checksum""

the checksum of a local file seems not to be the same like the file at the update servers.

i found that file in question (comps-f8.xml) in /var/cache/yum/updates
(this directory is cleaned by "yum clean all" by the way)

the checksum that is expected by pirut and co is obtained from: repomd.xml (within the same directory)

in repomd.xml you may find:
[...]
<data type="group">
<location href="repodata/comps-f8.xml">
<checksum type="sha">fea3dc6aef34f316fdf61d1e9ac2a61faae7e35c</checksum>
<timestamp>1194644692</timestamp>
</location>
</data>
[...]


I do not know why the checksum is wrong and what is the cause but
apparently you have the following choices:

find out the correct checksum of your comps-f8.xml file and put it into the repomd.xml
or
manage to disable the update repository - because this file seems to be connected to the update repository only.

I managed the latter one and at least now I am able to start yumex and pirut and co. without hanging - but I am not able to use the update repository (yet).

/h.

yeoheric
28th November 2007, 03:44 AM
In other words, F8 is pretty much screwed or the servers are. I am sorry to sound ungrateful, you know F8 being free and all, but this bug is annoying.

Bob, I am happy to run my updates from the CLI, but I ma just saying it's like taking three steps back. Unless I am running a server, I should not be troubled by the CLI much.

If other smaller distros can do it, I am sure the intelligent folks at RH and the Fedora community can do it as well. It is a real shame. I really do like F8.

Eric

bob
28th November 2007, 03:53 AM
Up to you of course. I should tell you that this is the first time I've experienced this problem with Yumex. However, if you choose to use another distro or another OS, it's your choice, which is what linux is all about.

bob
28th November 2007, 04:15 AM
HOLY MOLY! I just gave it one more try and ..... in the midst of failing...it started working!!!! I'd clear the metadata one more time, to be sure, but I think the mess is cleared up.

rayneitami
28th November 2007, 04:18 AM
as the error message says
comps-f8.xml:
23:47:15 : --> [Errno -1] Metadata file does not match checksum""

the checksum of a local file seems not to be the same like the file at the update servers.

i found that file in question (comps-f8.xml) in /var/cache/yum/updates
(this directory is cleaned by "yum clean all" by the way)

the checksum that is expected by pirut and co is obtained from: repomd.xml (within the same directory)

in repomd.xml you may find:
[...]
<data type="group">
<location href="repodata/comps-f8.xml">
<checksum type="sha">fea3dc6aef34f316fdf61d1e9ac2a61faae7e35c</checksum>
<timestamp>1194644692</timestamp>
</location>
</data>
[...]


I do not know why the checksum is wrong and what is the cause but
apparently you have the following choices:

find out the correct checksum of your comps-f8.xml file and put it into the repomd.xml
or
manage to disable the update repository - because this file seems to be connected to the update repository only.

I managed the latter one and at least now I am able to start yumex and pirut and co. without hanging - but I am not able to use the update repository (yet).

/h.

i replaced that with
<data type="group">
<location href="repodata/comps-f8.xml"/>
<checksum type="sha">ffc1f599da0dc48779a86cccbb4dc7d631f9c433</checksum>
<timestamp>1196091232</timestamp>
</data>
and it started working

robatino
28th November 2007, 04:45 AM
Bugzilla Bug 336461: Metadata file does not match checksum

https://bugzilla.redhat.com/show_bug.cgi?id=336461

Bugzilla Bug 374801: comps-f8.xml corrupt and so yum-updatesd continually re-downloads it

https://bugzilla.redhat.com/show_bug.cgi?id=374801

rayneitami
28th November 2007, 04:57 AM
i guess changing the hash like i did works for now and when then manage to fix the file and hash then all you'd have to do should a "yum clean all"

Lvcoyote
28th November 2007, 04:58 AM
F8 and yum have done it to me too..... seems a lot of people are having yum issues. Someone should point the developers to all these Yum threads on here.

BigNeil
28th November 2007, 09:22 PM
Looks like the comps-f8.xml file on all the mirrors is not a valid xml document (not well formed) it looks like a spelling mistake in the tags. If you try loading comps-f8.xml in firefox you get

XML Parsing Error: mismatched tag. Expected: </packckagereq>.
Location: http://ftp.riken.jp/Linux/fedora/updates/8/i386/repodata/comps-f8.xml
Line Number 3488, Column 44: <packckagereq type="optional">gobby</packagereq>
-------------------------------------------^
I'm guessing that packckagereq should probably read packagereq

BigNeil
28th November 2007, 09:56 PM
On further investigation the comps-f8.xml is valid at download.fedora.redhat.com but invalid on the mirrors (or at least the half dozen I tried)

edit this file
/etc/yum.repos.d/fedora-updates.repo

near the top in the [updates] section

change
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/SRPMS/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-source-f$releasever&arch=$basearch

to

baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/SRPMS/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-source-f$releasever&arch=$basearch

After this yumex works fine.

JohnBailey
29th November 2007, 04:53 AM
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/SRPMS/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-source-f$releasever&arch=$basearch

After this yumex works fine.

Doesn't that shift the yum search from the mirrors to the main Fedora download? In which case I would assume that they will fix it shortly. The fix suggested by rayneitami suggested seems to work for now. Although when I clicked on Groups in Yumex, the app crashed.

From the messages, would I be correct in guessing that the reason that yum from the CLI works because it doesn't sort everything into groups like both "Add and remove programs", the update scanner, and "Yumex" do?

yeoheric
29th November 2007, 10:26 AM
As stated I don't feel like changing distros; but F8 is genuinely a pretty distro. The fonts are rendered great, the general feeling is good.... and by the way yumex is working again now....

Guess it is really the servers' fault.

F8 is really one tough distro to move away from.

BigNeil
29th November 2007, 12:55 PM
Note that the following is based on empirical evidence, I don't actually KNOW that this is happening.
The mirrorlist URL gives a list of URL's for mirrored repositories, and each request returns a different list (possibly same ones in a different order, probably for load balancing) also for me I get mirrors in Europe (I'm in the UK)
(try it with http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-source-f8&arch=i386)

From a couple of tests I can find repositories that have removed the comps-f8.xml file ( and also removed the groups entry in the /repodata/repomd.xml file) I've also found some that still have an invalid comps-f8.xml. I suppose it will sort itself out over time

Have you noticed that some days you get updates very quickly and other days not so quick ?
The mirrors give radically different response times for me, so what I'm going to do is find the fastest one for me (which may well be physically close as well) and put that in as my baseurl.

jbannon
30th November 2007, 01:20 AM
It's working now

Lvcoyote
30th November 2007, 05:01 AM
I did a fresh install of F8 tonight, immediately after getting to the desktop I stopped the updatesd service. Then I did the following commands to get repositories


yum install yumex yum-fastestmirror yum-skip-broken yum-fedorakmod yum-kernel-module yum-refresh-updatesd

followed by

rpm -ivh http://rpm.livna.org/livna-release-8.rpm


That part went fine....... then I opened the yum extender and immediately got the multiple attempts to connect to different mirrors, all failed and finally timed out with:

Failure: repodata/comps-f8.xml from updates [errno 256] no more mirors to try.

This again is a clean install with no additional programs or anything yet.

Yum is broken big time with F8. Any new installs at this time are fruitless if you expect to get updates or any additional packages. Just thought I'd post this info in case anyone else is thinking of loading F8....... move on to something else. Its been almost a week and this is still fubar'd!!

BigNeil
30th November 2007, 10:04 AM
This again is a clean install with no additional programs or anything yet.

Yum is broken big time with F8. Any new installs at this time are fruitless if you expect to get updates or any additional packages.

Given that the problem is with the mirrors I don't know what you expected to happen with a fresh install.

yum is NOT broken, there seems to be a problem with the mirrors at the moment which affects the various GUI updaters (inc. yumex), but yum itself works fine

If you do what I said before, edit /etc/yum.repos.d/fedora-updates.repo and change from mirrorlist to baseurl then everything works fine. This is just a temporary fix until the mirrors problem is fixed.

F8 is an impressive release, once installed and updated (great instructions on http://www.howtoforge.com/), it looks good, plays all sorts of audio/video, supports a vast range of hardware, has an enormous range of software and all for FREE!! And it's probably going to save me from ever having to upgrade to Vista :)