The openoffice-bin-1.1.0.ebuild does not seem to check the return code from the installer, and thus merges even broken openoffice installations into the system. See error messages below. Reproducible: Always Steps to Reproduce: 1. Fill up your the device which contains /var/tmp/portage 2. emerge openoffice-bin 3. Actual Results: The installer fails with 'not enough space on the destiantion drive ExitCode: 20' but the ebuild goes on the with the installation normaly. Expected Results: The ebuild should exit with an error, and do not try to merge the installation. Sorry i had to copy it from the screen, because no mouse available on the system. ... >>> Install openoffice-bin-1.1.0 into /var/tmp/portage/openoffice-bin-1.1.0/image/ category app-office * Installing OpenOffice.org into build root... * Scanning for a open DISPLAY to start Xvfb... * Starting Xvfb on $DISPLAY=0 ... glibc version: 2.3.2 Initializing installation program.................... not enough space on the destination drive ExitCode: 20 * Removing build root from registry... grep: /var/tmp/portage/openoffice-bin-1.1.0/image//opt/OpenOffice.org1.1.0/*: No such file or directory * Fixing permissions... chmod: failed to get attributes of [lots of 'no such file or directoy' error message.. sorry i'm to lazzy to type them in all] >>> app-office/openoffice-bin-1.1.0 merged.
I have added a ||die statement, so this shouldn't happen anymore.
