Emerging app-emulation/vmware-player-2.5.0.118166 in a screen-session fails due to problem in ebuild. Reproducible: Always Steps to Reproduce: 1.screen 2.emerge vmware-player 3. Actual Results: # emerge vmware-player Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) app-emulation/vmware-player-2.5.0.118166 to / * VMware-Player-2.5.0-118166.x86_64.bundle RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking VMware-Player-2.5.0-118166.x86_64.bundle ;-) ... [ ok ] * * ERROR: app-emulation/vmware-player-2.5.0.118166 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * vmware-player-2.5.0.118166.ebuild, line 68: Called die * The specific snippet of code: * die "Please emerge this package using a different terminal" * The die message: * Please emerge this package using a different terminal * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-emulation/vmware-player-2.5.0.118166/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-player-2.5.0.118166/temp/die.env'. * Expected Results: emerging app-emulation/vmware-player-2.5.0.118166 I checked with the ebuild line 67-69 there is this if: 67 if [ "$(python -c "import curses; curses.setupterm(); print curses.tigetstr('hpa')")" == "None" ]; then 68 die "Please emerge this package using a different terminal" 69 fi Calling the python in the screen delivers: # python -c "import curses; curses.setupterm(); print curses.tigetstr('hpa')" None # echo $TERM screen The same out of a screen-session: # python -c "import curses; curses.setupterm(); print curses.tigetstr('hpa')" %p1%dG # echo $TERM xterm
Forgot to mention: emerge vmware-player out of a screen session works fine and as expected.
Apparently that's a feature of the ebuild, a workaround to the build system... But maybe it's not apparent enough that it's a feature?
Heinrich, you're correct. Vmware-player-2.5 and vmware-workstation-2.5 won't build in screen, because vmware's python installer will die midway through since it never expected None to be returned for the value tested. To avoid people complaining about vmware mysteriously rolling back, I added a check in, warning users to build vmware-player in a different terminal. Therefore: please build vmware in a different terminal. I'm going to mark this as INVALID, since it's not really a bug, it's trying to help you. If you feel that something could be done to improve the situation, please feel free to re-open this bug, and let me know...
Personally I don't think this should be marked as INVALID. Although the spesific reason emerge stops is a feature, the underlying problem still exits, and it still breaks emerge. In my opinion the bug should be reopened until a fix for the underlying problem has been found, and the feature can be removed again.
