okay the story goes like this: i grabbed spiders gnome-2 ebuilds and installed them. everything was fine. later, i wanted to merge a few more packages of gnome2, and i issued an appropriate --fetchonly command on tty1 (cause it takes very long to download stuff with dialup). back in x11 i chatted with spider about some gnome-2 issues, and that was the point when stuff got strange: my box froze - completely. no lan, no mouse, no keyboard - nothing worked. showed me a frozen X11 and that was pretty much it. after 1 minute of waiting, i resetted it and booted it back up. i was angry about my lost uptime and issued the same emerge -f command again. i wondered, cause emerge froze after the first or second line of output. it said "Merging foo to /" (or something similar - you know what i mean) and showed a blinking cursor. funny. i checked `top` and it showed a sandbox process which used 99% of my cpu. after 2-3 minutes, i ctrl-c'ed out of the stalled emerge. i tried to `ebuild portage-1.9.1.ebuild merge` by hand, but it stalled after the compilation. so i grabbed a binary package of portage (1.9.1) and tar jxvf'ed it to /, overwriting all traces of my old portage. the same thing happened again - it simply stalled. after that i tried `emerge --clean rsync` but that didnt help either. stuff like `emerge -s` still works - but i'm unable to merge anything new (and thats why i dont try to unmerge stuff, heh) i rebooted a few minutes ago, and now `emerge --debug portage` gives me this output: root@gravity etc # emerge --debug portage Calculating dependencies ...done! >>> emerge sys-apps/portage-1.9.1 to / !!! emerge aborting on /usr/portage/sys-apps/portage/portage-1.9.1.ebuild . root@gravity etc # lol, why does it abort? it's nice that sandbox doesnt stall anymore, but whats wrong now? ~sigh~ i dont want to reinstall. :( -phoen][x-
btw, "ebuild portage-1.9.1.ebuild merge" says: root@gravity portage # ebuild portage-1.9.1.ebuild merge root@gravity portage # unpack/install/compile dont work either. -phoen][x-
okay i edited conf files for hours now, and it seems that i stumbled about something which helps me: i had an rc6 make.globals.backup in my /etc (backups are nifty). i was so desparate that i copied it to /etc/make.globals (with backing the 1.0 version up before, of course) portage worked with this file, so i diffed it and merged it by hand (line by line). this line makes my portage act so weird: # Default user options FEATURES="sandbox" if i comment FEATURES="sandbox", it works like a charm. good for me - but i never ever edited this file by hand before. and there was no portage update lately, so this line has to be in there for like a few weeks (wild guess) - why did it work before, and what can i do to make portage work with this line again? btw, what is this line good for anyways? does it completely disable sandboxing? cant think of that.. -phoen][x-
IF you remove your /etc/ld.so.preload file before starting portage it should fix it.
This will be fixed in Portage 1.9.2
reopened this bug cause of this: removing the /etc/ld.so.preload and uncommenting the FEATURES="sandbox" line in /etc/make.globals make emerge stall again. (with the mysterious 99% sandbox process). however, if i rm /etc/ld.so.preload and do not uncomment the FEATURES-line, emerge will work. There seems to be something really wrong.. -phoen][x- (or am i supposed to not uncomment FEATURES?)
i updated to portage 1.9.2 a minute ago, but this didnt help too. i'll try your reboot trick later, but i fear that it wont help me. -phoen][x-
phoen][x reports this as a non-issue now anyway
