I usually run emerge --update --deep world in the background; updating to junit-3.8.1-r3 paused at the following point. Foregrounding the process resumed the copying (as evidenced); I was able to re-background the emerge after the "copying" phase completed [...] [javadoc] Generating /dev/shm/portage/junit-3.8.1-r3/work/junit3.8.1/junit3.8.1/javadoc/help-doc.html... [javadoc] 2 warnings [copy] Copying 20 files to /dev/shm/portage/junit-3.8.1-r3/work/junit3.8.1/junit3.8.1/doc [copy] Copying 1 file to /dev/shm/portage/junit-3.8.1-r3/work/junit3.8.1/junit3.8.1 [copy] Copying 1 file to /dev/shm/portage/junit-3.8.1-r3/work/junit3.8.1/junit3.8.1 [1]+ Stopped emerge --resume --skipfirst >>/tmp/2006-11-23-world.out 2>&1 && echo -ne "*** emerge done" [java] ......................................... [java] ......................................... [java] ..................................... [java] Time: 39.258 [java] OK (119 tests) BUILD SUCCESSFUL Total time: 5 minutes 29 seconds >>> Source compiled. >>> Test phase [not enabled]: dev-java/junit-3.8.1-r3 >>> Install junit-3.8.1-r3 into /dev/shm/portage/junit-3.8.1-r3/image/ category dev-java [...]
Yeah I was able to reproduce with 3.8.2 too.
junit-3.8.2-r1 also hangs when installing in background. Bringing it to the foreground allows it to continue.
What do you put emerge in background for? Why do you not run it in a separate shell like 99% of common users? I mean: Why? Nonsensical behaviour with Portage will result in unpredictable outcomes. This is not a bug, this is not even a feature of Portage. Just open a terminal, login as root, emerge junit and leave it finish. Closing this bug.