Hi, On Thu, 03 Sep 2015, Johannes Schauer wrote: > Using sbuild-shell I opened a shell in a local sid chroot and changed the > owner > of /var/lib/sbuild/ to root and removed all read and write access for > everybody. But even after that I was able to build a package!
Did you change the owning group as well? Because I can re-trigger it as easily as this: $ sudo chown -R root:root /srv/chroots/sid-amd64-sbuild/var/lib/sbuild $ sbuild -d unstable hello_2.10-1.dsc Note however that my unstable-amd64-sbuild chroot uses "union-type=overlay". It might be relevant... $ cat /etc/schroot/chroot.d/sid-amd64-sbuild # File managed by Salt. Do not edit manually. [sid-amd64-sbuild] type=directory description=Debian sid/amd64 directory=/srv/chroots/sid-amd64-sbuild aliases=unstable-amd64-sbuild,experimental-amd64-sbuild groups=root,sbuild profile=sbuild root-groups=root,sbuild source-root-groups=root,sbuild union-type=overlay > Investigating further, this seems to be because `chown -R sbuild:sbuild > /var/lib/sbuild` is already run in lib/Sbuild/ChrootSetup.pm (at least this > explains why it works for me). Are you sure this doesn't occur after the try to create the apt.conf file? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
