On Thu, Feb 11, 2021 at 02:08:15PM +0100, Johannes Schauer Marin Rodrigues wrote: > Quoting Julian Gilbey (2021-02-11 10:59:24) > > On Thu, Feb 11, 2021 at 10:36:14AM +0100, Sebastian Ramacher wrote: > > > > I am using schroot mode; my /etc/sbuild/sbuild.conf has $chroot_mode > > > > commented out, and I have set up an schroot called "sid-sbuild" with > > > > an alias "unstable-sbuild": > > > > > > > > [sid-sbuild] > > > > type=directory > > > > description=Debian sid sbuild > > > > directory=/srv/chroot/sid-sbuild > > > > groups=root,sbuild > > > > root-groups=sbuild > > > > aliases=unstable-sbuild > > > > > > This is missing a profile=sbuild. > > Awesome, nice find! I missed that. > > > Oh. That has fixed the problem. I wonder how that got lost? > > Did you write that file manually instead of using sbuild-createchroot or > sbuild-debian-developer-setup?
I honestly don't remember how I created it, though I do know I created it on a testing system on Tue Dec 29 2020.. I assume I would have used sbuild-createchroot, but if not, I don't know where I would have found out how to create a working sbuild chroot on my own. Anyway, I just created a new chroot using sbuild-createchroot and this was the perfectly sensible result: [bullseye-amd64-sbuild] description=Debian bullseye/amd64 autobuilder groups=root,sbuild root-groups=root,sbuild profile=sbuild type=directory directory=/srv/chroot/bullseye-sbuild union-type=overlay So I don't know where my one came from, but it looks at least heavily edited, and more likely hand-written. I also note a few other differences: * my one does not have "root" in root-groups * I have included an alias * I don't have a "union-type" setting Best wishes, Julian
