I use lvm and have a 9 GB partition mounted on /var/tmp, which was enougth to compile all the previous version. But app-office/libreoffice-3.4.4.2-r1 checks for 9 GB of space on /tmp, and then fails as my /tmp is only 1 GB or so. Why is the ebuild checks space in /tmp, and not in /var/tmp as before? Reproducible: Always Actual Results: >>> Running pre-merge checks for app-office/libreoffice-3.4.4.2-r1 * Checking for at least 1 gibibytes RAM ... [ ok ] * Checking for at least 9 gibibytes disk space at "/tmp/tmp3lZrI8/portage/app-office/libreoffice-3.4.4.2-r1/temp" ... [ !! ] * There is NOT at least 9 gibibytes disk space at "/tmp/tmp3lZrI8/portage/app-office/libreoffice-3.4.4.2-r1/temp" * * Space constrains set in the ebuild were not met! * The build will most probably fail, you should enhance the space * as per failed tests. * * ERROR: app-office/libreoffice-3.4.4.2-r1 failed (pretend phase): * Build requirements not met! * * Call stack: * ebuild.sh, line 56: Called pkg_pretend * libreoffice-3.4.4.2-r1.ebuild, line 228: Called check-reqs_pkg_pretend * check-reqs.eclass, line 105: Called check-reqs_pkg_setup * check-reqs.eclass, line 96: Called check-reqs_output * check-reqs.eclass, line 237: Called die * The specific snippet of code: * [[ ${EBUILD_PHASE} == "pretend" && -z ${I_KNOW_WHAT_I_AM_DOING} ]] && \ * die "Build requirements not met!" * * If you need support, post the output of 'emerge --info =app-office/libreoffice-3.4.4.2-r1', * the complete build log and the output of 'emerge -pqv =app-office/libreoffice-3.4.4.2-r1'.
maybe a duplicate of https://bugs.gentoo.org/show_bug.cgi?id=388593 what version of portage are you using?
Created attachment 292195 [details] emerge --info Attached emerge --info, I use the current stable portage version (2.1.10.11). I was able to compile it with: I_KNOW_WHAT_I_AM_DOING=1 emerge -DuvaN world So the ebuild is compiled in the correct /var/tmp directory, just the check is wrong at the beginning.
(In reply to comment #2) > Attached emerge --info, I use the current stable portage version (2.1.10.11). bug 388593 is only fixed in 2.1.10.32 and 2.2.0_alpha72
*** This bug has been marked as a duplicate of bug 388593 ***
