Your message dated Thu, 10 Apr 2025 07:02:36 +0200
with message-id <174426135648.1395460.17422735126787733458@localhost>
and subject line Re: sbuild: unshare mode uses wrong user for "Check disk
space" commands when $build_user is set
has caused the Debian Bug report #1032046,
regarding sbuild: unshare mode uses wrong user for "Check disk space" commands
when $build_user is set
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1032046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032046
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.85.0
Severity: normal
X-Debbugs-Cc: [email protected]
Using the following sbuild.conf:
$chroot_mode = 'unshare';
$build_user = 'user7777';
Results in this error:
Check disk space
----------------
runuser: user vagrant does not exist or the user entry does not contain all
the required fields
E: read_command failed to execute du
Use of uninitialized value $current_usage in scalar chomp at
/usr/share/perl5/Sbuild/Build.pm line 2271.
E: du exited with non-zero exit status 256
runuser: user vagrant does not exist or the user entry does not contain all
the required fields
E: read_command failed to execute du
E: Cannot determine space needed for /<<PKGBUILDDIR>> (du failed)
If I add the following to sbuild.conf:
$external_commands = {
"chroot-setup-commands" => [
['useradd', '--uid', '1000', '--user-group', '--shell', '/bin/bash',
'--groups', 'sbuild', 'vagrant' ],
]};
Then it works for me, and actually builds as the user specified with
$build_user.
Seems like it should also use $build_user for the check disk space
command as well!
live well,
vagrant
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sbuild depends on:
ii adduser 3.131
ii libsbuild-perl 0.85.0
ii perl 5.36.0-7
Versions of packages sbuild recommends:
pn autopkgtest <none>
pn debootstrap <none>
pn schroot <none>
ii uidmap 1:4.13+dfsg1-1
Versions of packages sbuild suggests:
pn deborphan <none>
ii e2fsprogs 1.46.6-1
ii kmod 30+20221128-1
ii wget 1.21.3-1+b2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.88.2
Hi,
On Sun, 26 Feb 2023 15:24:13 -0800 Vagrant Cascadian
<[email protected]> wrote:
> Using the following sbuild.conf:
>
> $chroot_mode = 'unshare';
> $build_user = 'user7777';
>
> Results in this error:
>
> Check disk space
> ----------------
>
> runuser: user vagrant does not exist or the user entry does not contain all
> the required fields
> E: read_command failed to execute du
> Use of uninitialized value $current_usage in scalar chomp at
> /usr/share/perl5/Sbuild/Build.pm line 2271.
> E: du exited with non-zero exit status 256
> runuser: user vagrant does not exist or the user entry does not contain all
> the required fields
> E: read_command failed to execute du
> E: Cannot determine space needed for /<<PKGBUILDDIR>> (du failed)
>
> If I add the following to sbuild.conf:
>
> $external_commands = {
> "chroot-setup-commands" => [
> ['useradd', '--uid', '1000', '--user-group', '--shell', '/bin/bash',
> '--groups', 'sbuild', 'vagrant' ],
> ]};
>
> Then it works for me, and actually builds as the user specified with
> $build_user.
>
> Seems like it should also use $build_user for the check disk space
> command as well!
this was fixed in sbuild 0.88.2 with commit
84b9e611a0ea130cfa27bd5a7ab4d68b95d3bff3.
Thanks!
cheers, josch
signature.asc
Description: signature
--- End Message ---
