Control: severity -1 important Hi,
Johannes Schauer <jo...@mister-muffin.de> (2018-10-06): > how did you create the chroot? Did you use sbuild-createchroot? > > I'm not yet able to reproduce your problem and sbuild's autopkgtest also seems > to pass just fine: https://ci.debian.net/packages/s/sbuild/unstable/amd64/ > > Did you read the EXAMPLES section of the sbuild man page? Or the man page of > sbuild-createchroot? > > Did you maybe try using sbuild-debian-developer-setup which is a script that > should setup your machine so that you can start building packages right away? > > Also: why are you attempting to run sbuild with sudo? I can reproduce this issue on a stretch system, installed with jessie then upgraded, with some tweaks. Accessing old chroots is OK, but the newly created stretch one isn't accessible: E: Access not authorized I: You do not have permission to access the schroot service. I: This failure will be reported. Chroot setup failed Error setting up stretch-amd64-sbuild chroot To get all possible tweaks out of the way, I've reproduced this on a clean stretch VM, with a default install using a 9.6.0 netinst image. Steps to reproduce, with a pre-existing cyril user: - as root: apt-get -y install sbuild sudo adduser cyril sbuild adduser cyril sudo - as cyril: sudo sbuild-createchroot stretch /home/sbuild/stretch-amd64-sbuild http://deb.debian.org/debian sudo mv /etc/schroot/chroot.d/stretch-amd-sbuild-<RANDOM> /etc/schroot/chroot.d/stretch-amd-sbuild sbuild-shell stretch-amd64-sbuild → “E: Access not authorized” sbuild-update -udcar stretch-amd64-sbuild → “E: Access not authorized” The same happens when replacing stretch with sid. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
