# FEATURES="-sandbox" emerge -av1 =sandbox-2.10* These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] sys-apps/sandbox-2.10-r2::gentoo [2.11-r2::gentoo] ABI_X86="32 (64) (-x32)" 0 KiB Total: 1 package (1 downgrade), Size of downloads: 0 KiB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-apps/sandbox-2.10-r2::gentoo * sandbox-2.10.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] /usr/lib/portage/python2.7/phase-functions.sh: line 234: 26789 Segmentation fault install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" * ERROR: sys-apps/sandbox-2.10-r2::gentoo failed (unpack phase): * Failed to create dir '/var/tmp/portage/sys-apps/sandbox-2.10-r2/work' * * Call stack: * ebuild.sh, line 780: Called __ebuild_main 'unpack' * phase-functions.sh, line 1005: Called __dyn_unpack * phase-functions.sh, line 240: Called die * The specific snippet of code: * * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.10-r2::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.10-r2::gentoo'`. * If configure failed with a 'cannot run C compiled programs' error, try this: * FEATURES=-sandbox emerge sandbox * The complete build log is located at '/var/tmp/portage/sys-apps/sandbox-2.10-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.10-r2/temp/environment'. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-apps/sandbox-2.10-r2/work/sandbox-2.10' >>> Failed to emerge sys-apps/sandbox-2.10-r2, Log file: >>> '/var/tmp/portage/sys-apps/sandbox-2.10-r2/temp/build.log' Things would work better if disabling sandbox disabled sandbox!
you failed to post `emerge --info` like every bug report is supposed to have, so i'm just going to assume you still have FEATURES=usersandbox.
So the message even suggests (for a slightly different failure mode): * try this: * FEATURES=-sandbox emerge sandbox Now we have *two* bugs ... And can you please stop closing valid bugs just because raisins? It's frustrating and doesn't fix issues.
(In reply to Patrick Lauer from comment #2) i can tweak the message in the sandbox ebuild, but the issue still remains: your request is invalid. you have FEATURES=usersandbox which you did not disable hence having an active sandbox is not a bug.
Nobody expects the spanish inquisition! Among our many issues are such issues as ... (1) FEATURES="-sandbox" emerge ... does not disable sandbox (2) FEATURES="-sandbox" should imply FEATURES="-ipc-sandbox -network-sandbox -usersandbox" (3) If those previous two issues are not changed then emerge prints a wrong message and should be fixed So that's between one and three issues that should be fixed.
(In reply to Patrick Lauer from comment #4) > (1) FEATURES="-sandbox" emerge ... does not disable sandbox Sandbox ebuilds have been updated: https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-apps/sandbox?id=a78f835745636e1ebee5a2cfae57673e4d46427c > (2) FEATURES="-sandbox" should imply FEATURES="-ipc-sandbox -network-sandbox > -usersandbox" I suppose we could support globs like FEATURES="-*sandbox" for this. Not sure that it's really worth the effort. Maybe a --sandboxes=n option would be more practical. Obviously, it's preferable that sandbox issues be fixed, rather than require users to manually disable sandboxes. > (3) If those previous two issues are not changed then emerge prints a wrong > message and should be fixed Do you mean the message that's already fixed in the sandbox ebuilds?
(In reply to Patrick Lauer from comment #4) you don't seem to understand what these different features do. only "sandbox" and "usersandbox" loads code via `sandbox` & libsandbox.so. if you actually read the manual/code, you'd see that ipc-sandbox & network-sandbox create linux namespaces only. as for the request to have FEATURES=-sandbox disable all sandboxes, the answer there is no. adding glob support seems like overkill for an issue that rarely comes up and impacts only one package (sandbox itself).
Glob -- no. And the ebuild message is fixed.
