glibc unmerged during emerge of wine/vmware/gcc

bison · n00b Joined: 07 Sep 2005 Posts: 16

I have managed to get my system into a state where emerging wine/vmware/gcc-3.4.4 all automaticaly unmerge glibc and break the system.
I can easily repair this from a backup (yeah for backups

) , but it is reliably reproducable. The entry in emerge.log is Unmerging sys-libs/glibc-2.3.4.20040808
I'm a bit lost on how to fix this, i.e. how to emerge wine or vmware without crashing the whole system.
Any and all suggestions most welcome.
_________________
Beware the muppet!

SinoTech · Posted: Fri Sep 09, 2005 11:55 am Post subject:

Hmm .. that's really interesting. A update to gcc or something similiar mustn't unmgere your glibc. Perhaps you've done a "world" update which also updates glibc to 2.3.5-r1 and therefore unmerged the old version ? But even if it do that, it shouldn't break your system.
How have you done the update ?

Mfg

Sino

ecatmur · Posted: Fri Sep 09, 2005 11:55 am Post subject:

What does emerge -pv wine show?
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

bison · n00b Joined: 07 Sep 2005 Posts: 16

Sorry for delay, I broke the boot loader and had to fix that first.

The output from

SinoTech · Posted: Sat Sep 10, 2005 9:22 am Post subject:

bison · n00b Joined: 07 Sep 2005 Posts: 16

SinoTech · Posted: Sat Sep 10, 2005 10:50 am Post subject:

Well, I am not sure, but I think of a corrupt ebuild file. I think there's somewhere a statement in it which causes emerge to unmerge glibc. I don't know if it is really possible to place such a statement in an ebuild but I can't think of another reason. Anyway, doing an "emerge --sync" should give you a correct portage tree back (For the case there's somewhere a hacked rsync server you hit at the last sync, there're good chances you hit a valid one at this time

).
But before doing a new sync, can you tar your portage tree and send it to me ? I would be really interested in that.

bison · n00b Joined: 07 Sep 2005 Posts: 16

I've found this old thread https://forums.gentoo.org/viewtopic-t-39502-postdays-0-postorder-asc-start-0.html
which seems to be related. I'm not sure if the people in this thread were actualy having their binaries removed (sounds painful

) or if it was a similar glibc problem to what I'm experiancing. <gulp> I'm going to have another go with AUTOCLEAN="no"</gulp>
_________________
Beware the muppet!

bison · n00b Joined: 07 Sep 2005 Posts: 16

Setting AUTOCLEAN to no seams to have stopped the problem for now (emerging wine worked

)
There seems to be a bit of history of this happening (I just couldn't find the threads initialy).
_________________
Beware the muppet!

SinoTech · Posted: Sun Sep 11, 2005 9:26 am Post subject:

Interesting. Could you post the output of "emerge --info" please.

Mfg

Sino

bison · n00b Joined: 07 Sep 2005 Posts: 16

ftp://mirror.pacific.net.au/linux/Gentoo

http://public.planetmirror.com/pub/gentoo

http://distfiles.gentoo.org

http://gentoo.osuosl.org

The only thing in this that I thought looked a bit dodgy was the "elibc_glibc" use flag. I couldn't find any info on this, but as I didn't add it I wasn't too keen to remove it. Bear in mind that this listing is after I added AUTOCLEAN="no" to make.conf. Prior to that it yas set to the default (yes).
_________________
Beware the muppet!

SinoTech · Posted: Mon Sep 12, 2005 10:38 am Post subject:

kallamej · Posted: Mon Sep 12, 2005 4:40 pm Post subject:

You seem to have two versions of glibc installed, you only need one as they're in the same SLOT. Unmerging the older version shouldn't create havoc. Is it so that the autoclean of the old glibc fails? In that case, please see the FAQ GF19 for how to proceed.

Seeing you have old portage and glibc versions, when was the last time you ran emerge sync?
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat

bison · n00b Joined: 07 Sep 2005 Posts: 16

Thanks, I'll try these suggestions tonight after work.

bison · n00b Joined: 07 Sep 2005 Posts: 16

I figured I'd tidy up my duplicate python/glibc versions before doing the sync. Good in theory, but not so great in practice.

kallamej · Posted: Tue Sep 13, 2005 5:22 am Post subject:

A corrupt tree would probably cause problems earlier. I'd try updating portage first. If http downloads are feasible you can use emerge-webrsync to fetch a snapshot of the portage tree. It should be at most 24 hours old.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat

bison · n00b Joined: 07 Sep 2005 Posts: 16

Still no joy.
Even after emerging portage to update it, tying to unmerge python-2.3.4 takes out python-2.3.5 as well.
Both times I've tried unmerging python-2.3.4 I've seen the following output

Does this mean it isn't distinguishing between the two versions of python? Would that be related to python being non slotted?
_________________
Beware the muppet!

kallamej · Posted: Wed Sep 14, 2005 9:53 am Post subject:

Some purging is to be expected, but not those... I'd file a bug.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat

bison · n00b Joined: 07 Sep 2005 Posts: 16

I have requested that bug 94132 be reopened. I don't know if that is the whole problem relating to this thread, but I think it's part of it.
_________________
Beware the muppet!

kallamej · Posted: Wed Sep 14, 2005 6:34 pm Post subject:

Hmm, I don't think that's it. That bug is about the warning only as far as I can tell. My understanding was that portage unmerges both your versions even if it says it will only unmerge one of them which is a different matter.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat

bison · n00b Joined: 07 Sep 2005 Posts: 16

Appologies for slow response.

bison · n00b Joined: 07 Sep 2005 Posts: 16

bug 107241 finally created.

_________________
Beware the muppet!