Bummer, sandbox file does not exist: /var/tmp/portage/dev-python/autobahn-20.7.1/temp/sandbox.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-20201031-121706 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.47.0 * The following VMs are available for generation-2: 1) IcedTea JDK 3.17.0 [icedtea-8] *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Fri Nov 6 02:05:31 PM UTC 2020 emerge -qpvO dev-python/autobahn [ebuild N ] dev-python/autobahn-20.7.1 USE="crypt -scram -test (-xbr)" PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
this seems to be either still an issue or a similarity to the one reported in bug 704754
Created attachment 670223 [details] emerge-info.txt
Created attachment 670226 [details] dev-python:autobahn-20.7.1:20201106-144249.log
Created attachment 670229 [details] emerge-history.txt
Created attachment 670232 [details] etc.portage.tbz2
Created attachment 670235 [details] logs.tbz2
Yes, this is the same issue as in the previous bug. From what I see, it is the pkg_postinst() running of twisted's plugin index regen since autobahn installs a twisted plugin. pkg_postinst() { python_foreach_impl twisted-regen-cache || die } Seems to me this should be an exception to your tinderbox sandboxing. Are no other pkgs that install twisted plugins causing this same violation?
hmm, actually I believe it is the index generation during autobahns install in the sandbox. before the actual install which the ebuild deletes this generated index to prevent the file collision of the twisted owned index file.
I am going to close this bug since this is only a tinderbox issue. It would otherwise require maintaining a patch that removes the regeneration of the twisted plugin db within setup.py
(In reply to Brian Dolbec from comment #9) > I am going to close this bug since this is only a tinderbox issue. It would > otherwise require maintaining a patch that removes the regeneration of the > twisted plugin db within setup.py Would it be possible to restrict the appropriate FEATURE ?
If you can come up with an appropriate sed or other easy means that can easily delete or disable the code starting at: https://github.com/crossbario/autobahn-python/blob/master/setup.py#L315 then by all means mod the ebuild. I suck at sed, that is 17 lines of code that may be subject to change in the future.
If upstream can accept a patch that optionally disables the regen, that would be easy to then disable via an environment variable in the ebuild. But I fear that this is too obscure a use case for it to be accepted.
ah ok, I thought that something like "restrict=sandbox" would make it in the ebuild itself (probably only for the additional sandbox features which are set by the tinderbox)
Does restrict=sandbox will fix it for you?
The tinderbox autoaatically re-tries sandbox failures by a package specific setting: <=dev-python/autobahn-20.12.3 nosandbox which indeed solves it for the tinderbox autoamtic :-)
(In reply to Toralf Förster from comment #15) > The tinderbox autoaatically re-tries sandbox failures by a package specific > setting: > > <=dev-python/autobahn-20.12.3 nosandbox > > which indeed solves it for the tinderbox autoamtic :-) which is technically: FEATURES="-sandbox -usersandbox"
So, this is a tinderbox specific setting? No need to RESTRICT="sandbox usersandbox" in the ebuild?
(In reply to Brian Dolbec from comment #17) > So, this is a tinderbox specific setting? No need to RESTRICT="sandbox > usersandbox" in the ebuild? No. The tinderbox sets in make.conf: FEATURES="xattr cgroup -news -collision-protect" So "sandbox" is a default settings of Gentoo for emerge IMO.
*** Bug 770448 has been marked as a duplicate of this bug. ***
(In reply to Brian Dolbec from comment #17) > So, this is a tinderbox specific setting? No need to RESTRICT="sandbox > usersandbox" in the ebuild? IMO you should restrict it in the ebuild - if autobahn doesn't emerged well with enabled sandbox
Maybe add an addpredict for that file.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=548c1482c748845e3dac7351d2e622fdce5727f4 commit 548c1482c748845e3dac7351d2e622fdce5727f4 Author: Brian Dolbec <dolsen@gentoo.org> AuthorDate: 2021-02-14 19:14:46 +0000 Commit: Brian Dolbec <dolsen@gentoo.org> CommitDate: 2021-02-14 19:15:25 +0000 dev-python/autobahn: Fix tinderbox sandbox issue Closes: https://bugs.gentoo.org/753338 Package-Manager: Portage-3.0.10, Repoman-3.0.2 Signed-off-by: Brian Dolbec <dolsen@gentoo.org> dev-python/autobahn/autobahn-21.2.1.ebuild | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-)
