This morning portage-2.2.00.13629 was emerged during bootstrapping. The next emerge operation failed as follows: * Package 'sys-apps/portage-2.2.00.13629' merged despite file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. [ text skipped ] >>> Emerging (1 of 1) app-admin/python-updater-0.6-r1 * python-updater-0.6.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] ACCESS DENIED open_wr: /var/opt/quest/vas/vasd/vas_misc.vdb ISE:write_logfile unable to append logfile ISE open_wr(/var/opt/quest/vas/vasd/vas_misc.vdb): No such file or directory abs_path: /var/opt/quest/vas/vasd/vas_misc.vdb res_path: /var/opt/quest/vas/vasd/vas_misc.vdb /local/tmp/j/usr/lib/libsandbox.so[0xb7fac476] /local/tmp/j/usr/lib/libsandbox.so[0xb7fac4ec] /local/tmp/j/usr/lib/libsandbox.so[0xb7fad6d9] /local/tmp/j/usr/lib/libsandbox.so[0xb7fadd62] /local/tmp/j/usr/lib/libsandbox.so(open64+0xae)[0xb7fb203e] /opt/quest/lib/libvas.so.4(vas_file_safeopen+0x74)[0xb7d19d6c] /opt/quest/lib/libvas.so.4(vassym_sqlite3OsOpenReadWrite+0x2f)[0xb7cb25af] /opt/quest/lib/libvas.so.4(vassym_sqlite3pager_open+0x39a)[0xb7cb506a] /opt/quest/lib/libvas.so.4(vassym_sqlite3BtreeOpen+0x42)[0xb7c9e3c2] /opt/quest/lib/libvas.so.4(vassym_sqlite3BtreeFactory+0x35)[0xb7cb15f5] /proc/14261/cmdline: /bin/bash -rcfile /local/tmp/j/usr/share/sandbox/sandbox.bashrc -c "/local/tmp/j/usr/lib/portage/bin/ebuild.sh" unpack Sandboxed process killed by signal: Aborted * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior * is known to be triggered by things such as failed variable assignments * (bug #190128) or bad substitution errors (bug #200313). Normally, before * exiting, bash should have displayed an error message above. If bash did * not produce an error message above, it's possible that the ebuild has * called `exit` when it should have called `die` instead. This behavior * may also be triggered by a corrupt bash binary or a hardware problem * such as memory or cpu malfunction. If the problem is not reproducible or * it appears to occur randomly, then it is likely to be triggered by a * hardware problem. If you suspect a hardware problem then you should try * some basic hardware diagnostics such as memtest. Please do not report * this as a bug unless it is consistently reproducible and you are sure * that your bash binary and hardware are functioning properly. >>> Failed to emerge app-admin/python-updater-0.6-r1, Log file: >>> '/local/scratch/portage/app-admin/python-updater-0.6-r1/temp/build.log'
what is /var/opt/quest? something installed by the host system?
(In reply to comment #1) > what is /var/opt/quest? something installed by the host system? > Yes, it is 3rd-party software that us users have no control over.
Then this is something host specific, for which you'll have to tell sandbox it is ok. I think adding a env.d entry with SANDBOX_PREDICT=/var/opt/quest/vas/vasd should do it.
(In reply to comment #3) Strange, why should the bootstrapping procedure care about things under /var/opt? I don't even have permission to create files in that directory. Oh well, I'll do some reading and see if I can create a workaround to start with.
