Terrible problem with emerge gnome

RATFOOD · n00b Joined: 19 Mar 2003 Posts: 44

Hey guys heres what happened to me. I emerged gnome and went to watch a crappy movie (The Core), Well when I get back look what happens!
When it is almost done it breaks the emerge and says that gentoo-gdm-theme.tar.bz2 md5 hash doesnt match!

So I do this:

#rm /usr/portage/distfiles/gentoo-gdm-theme.tar.bz2
#emerge gnome

and I get the same error!! (?)

so I change to next mirror (cause I think oregon state has a bad hash) and I get the same error there too!.

any ideas what a guys supposed to do??
:?:

David_Escott · l33t Joined: 12 Jan 2003 Posts: 952 Location: Boston, MA

two possibilities

either your downloading problem is breaking the file (I have seen prozilla do this with some ftp servers)

the md5 sum is just wrong in which case feel free to make your own
cd in to the directory of the ebuild and run

ebuild gdm-whatever-x.y.ebuild digest

sryan2k1 · n00b Joined: 03 Apr 2003 Posts: 10

mine did this also, after freaking out and working on it for about 1/2 hour heres what you do, delete the file it tells you to,

RATFOOD · n00b Joined: 19 Mar 2003 Posts: 44

ok, i'll try anything but what you just said is greek to me...
Can someone tell me how to do this??

I tried ebuild gentoo-gdm-...etc digest and it says
"!!!doebuild: (above) doesn't seem to be an ebuild file"

I will be glad to override the md5 if someone can please tell me how

thanks David & guys

RATFOOD · n00b Joined: 19 Mar 2003 Posts: 44

ok syran, thanks, im trying it now

David_Escott · l33t Joined: 12 Jan 2003 Posts: 952 Location: Boston, MA

the md5 is just a way of adding up all the values in the file to try and figure out if the file has been changed in any way. If during the download the file is messed up then the md5 will catch this before you start building. You download md5 sums with the rest of the portage tree when you sync. Sometimes however these get messed up in portage (usually someone getting forgetful or careless). It is an easy thing to correct when it does mess up. Running ebuild file.ebuild digest on the ebuild file which is complaining about a bad download should fix it. It sounds like you ran it on gdm's directory not the gdm ebuild file. The other solution is to wait a few hours until the md5 sums are fixed upstream and you can sync back up.

sryan2k1 · n00b Joined: 03 Apr 2003 Posts: 10

yes but its allready been fixed and a emerge sync will fix u up

Jarjar · Apprentice Joined: 21 Jul 2002 Posts: 265 Location: Sweden

Heh.. I did it the "hard" way.
I confirmed that the file was valid, got the correct MD5 and edited, now it works.

Although GNOME doesn't work yet..

_________________
[Server etc. | C2D 2.2 @ 3.0 GHz / 4 GB RAM / 3x1 TB + 1x2 TB SATA disks + 1.5 TB ext. | Gentoo]
[Laptop | Macbook Pro 15" / Core i7 (Sandy) Quad 2.2 GHz / 16 GB RAM / Samsung 840 250 GB SSD + 1 TB + 2 TB HDD / 6750M 1 GB / OS X, Win 7]

RATFOOD · n00b Joined: 19 Mar 2003 Posts: 44

OK thanks everyone... I did "emerge sync" like Sryan said and that fixed everything. I don't know how it got messed up like that but at least I know how to fix it. Gnome is working like a champ now

M.A. · Posted: Tue Apr 08, 2003 11:36 pm Post subject:

I seems that it's the same problem others had wtih gdm compilation.
See https://forums.gentoo.org/viewtopic.php?p=273341#273341

I think it's a better solution than just doing 'emerge sync', as you would not lose your old portage tree.