Hi Niels,
Quoting Niels Thykier (2025-04-21 22:13:32)
> Of the options presented, I would recommend the first one.
>
> That option has my preference because:
>
> A) It does not present an error to be ignored. I do not like such
> behavior since I feel it promotes error blindness. The thir
Johannes Schauer Marin Rodrigues:
Control: tag -1 + moreinfo
Hi,
[...]
yes, in the code there is this comment right after the "rm -rf" runs:
# we ignore the exit status, because the command will fail to remove the
# unpack directory itself because of insufficient permissions
It would be nic
Control: tag -1 + moreinfo
Hi,
On Mon, 21 Oct 2024 13:25:33 +0200 Niels Thykier wrote:
> The sbuild code assumes that the directory hosting the
> UNSHARE_TMPDIR_TEMPLATE is mode 4777 (--chroot-mode=unshare). When it is
> not, the following rm failure will appear under cleanup
>
> > +-
I also just hit something like this -- /dev/shm had somehow been unmounted
(not due to sbuild) and so the chroot could not be unpacked --- the build
fails but there was no info about why, not even "could not unpack the
chroot", so something is throwing away the error message
Package: sbuild
Version: 0.86.2
Severity: minor
X-Debbugs-Cc: ni...@thykier.net
Hi
The sbuild code assumes that the directory hosting the
UNSHARE_TMPDIR_TEMPLATE is mode 4777 (--chroot-mode=unshare). When it is
not, the following rm failure will appear under cleanup
+--
5 matches
Mail list logo
