Package: sbuild Version: 0.78.0-2 Severity: minor Hi,
Please consider setting umask to 0022 in sbuild-createchroot. My root has 0027, and together with schroot of type=lvm-snapshot, this results in an unusable chroot. The first indication is an EPERM when finishing up: $ umask 0027 $ sbuild-createchroot sid --chroot-prefix=sidtest sidtest-amd64-sbuild http://localhost:9999/debian | I: Setting reference package list. | I: Updating chroot. | Hit:1 http://localhost:9999/debian sid InRelease | Get:2 http://localhost:9999/debian sid/main Sources [8909 kB] | Fetched 8909 kB in 3s (2753 kB/s) | Reading package lists... Done | W: Download is performed unsandboxed as root as file'/var/lib/apt/lists/partial/localhost:9999_debian_dists_sid_InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Using this schroot with type=lvm-snapshot, sbuild terminates almost immediately after attempting a build: $ sbuild -c sidtest-amd64-sbuild *.dsc | E: Failed to change to directory ‘/’: Permission denied | I: The directory does not exist inside the chroot. Use the --directory option to run the command in a different directory. | E: read_command failed to execute dpkg | Use of uninitialized value $chroot_arch in scalar chomp at /usr/share/perl5/Sbuild/Build.pm line 3024. | E: Can't determine architecture of chroot: With a umask of 0022, the problem goes away. Regards, Christian
