https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: net-wireless/kismet-2022.08.1-r1 sandbox violation. Discovered on: amd64 (internal ref: tinderbox_musl) NOTE: This machine uses MUSL libc
Created attachment 813922 [details] build.log build log and emerge --info
Created attachment 813925 [details] 1-sandbox.log 1-sandbox.log
Error(s) that match a know pattern: error: [Errno 13] Permission denied error: [Errno 13] Permission denied
This doesn't fit the usual pattern of a sandbox violation, looks like it's failing to set time on a file or something? copying build/lib/KismetCaptureRtl433/kismetexternal/__init__.py -> //var/tmp/portage/net-wireless/kismet-2022.08.1-r1/image/usr/lib/python3.10/site-packages/KismetCaptureRtl433/kismetexternal * ACCESS DENIED: utimensat: /var/tmp/portage/net-wireless/kismet-2022.08.1-r1/image/usr/lib/python3.10/site-packages/KismetCaptureRtl433/kismetexternal/__init__.py error: [Errno 13] Permission denied
since I didn't know what this was, here is a reference: https://man7.org/linux/man-pages/man2/utimensat.2.html
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad8912f229d715cbb71e45020470b73519a9a836 commit ad8912f229d715cbb71e45020470b73519a9a836 Author: Rick Farina <zerochaos@gentoo.org> AuthorDate: 2023-01-04 20:17:34 +0000 Commit: Rick Farina <zerochaos@gentoo.org> CommitDate: 2023-01-04 20:18:36 +0000 net-wireless/kismet: remove unneeded sed Bug: https://bugs.gentoo.org/872608 While investigating bug #872608 it was found that this sed is no longer needed. Removing the unneeded sed. Signed-off-by: Rick Farina <zerochaos@gentoo.org> net-wireless/kismet/kismet-2022.08.1-r1.ebuild | 6 +----- net-wireless/kismet/kismet-9999.ebuild | 6 +----- 2 files changed, 2 insertions(+), 10 deletions(-)
In #gentoo-dev, we determined that this is triggered by musl's realpath implementation, which does not remove duplicate slashes from the input. If a program performs a filesystem operation on a path with duplicate slashes, libsandbox will fail to remove them, and the access check will fail.
Upstream kismet accepted a patch from me to remove the double slash. I'm not applying it to the versioned release because the kismet maintainer is planning an updated release soon anyway. This ends my involvement here as I can't replicate the issue and I would personally consider it a sandbox/musl issue. Bug was already reassigned away from me, I just wanted to close the loop on the part relating to my package. Thanks for the report.
*** Bug 895774 has been marked as a duplicate of this bug. ***
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eac4803723e269b65bed0847b3e57924d347d340 commit eac4803723e269b65bed0847b3e57924d347d340 Author: Rick Farina <zerochaos@gentoo.org> AuthorDate: 2023-02-22 20:42:30 +0000 Commit: Rick Farina <zerochaos@gentoo.org> CommitDate: 2023-02-22 20:44:36 +0000 net-wireless/kismet: fixup deps Adjust deps per qa tools Remove do nothing sed lines Use bundled libfmt Closes: https://bugs.gentoo.org/872608 Signed-off-by: Rick Farina <zerochaos@gentoo.org> .../files/kismet-2022.08.1-sandbox-fix.patch | 147 +++++++++++++++ net-wireless/kismet/kismet-2022.08.1-r2.ebuild | 208 +++++++++++++++++++++ net-wireless/kismet/kismet-9999.ebuild | 32 ++-- 3 files changed, 369 insertions(+), 18 deletions(-)
I think we should keep this open for fixing sandbox itself.
I'm not 100% sure if sandbox wants to resolve this, or just if they consider a musl bug or whatever. My part here is fixed upstream and in gentoo, so I am fine with whatever the sandbox maintainers decide.
*** Bug 896070 has been marked as a duplicate of this bug. ***
