Hi, Quoting Samuel Thibault (2016-08-31 19:20:54) > Johannes Schauer, on Wed 31 Aug 2016 19:11:38 +0200, wrote: > > Additionally, current sbuild only seem to have this message in > > lib/Sbuild/ChrootPlain.pm and lib/Sbuild/ChrootSudo.pm. Are you not using > > schroot for your chroots? > > I'm not sure what you exactly mean. AIUI I'm using plain directory > chroots with a mere sudo chroot into it, nothing fancy like schroot sessions, > snapshots, fresh tarball etc. I just use sbuild to launch it.
if your setup deviates from the default, please include in your bugreport how it does. For example in your case, how does your ~/.sbuildrc look like. Or even better: can you figure out which setting in your ~/.sbuildrc that is different from the default creates your problem? You could just backup your current ~/.sbuildrc and start from a fresh one and then modify it until you found out how your setup deviates from the default. I thought you were using schroot because you earlier said that you were using a type=directory chroot. This is syntax that you would put into your schroot config. For example I have: [unstable-amd64-sbuild] description=Debian unstable/amd64 autobuilder groups=root,sbuild root-groups=root,sbuild profile=sbuild type=directory directory=/srv/chroot/unstable-amd64 union-type=overlay Did you not create your chroot with sbuild-createchroot? It is not unlikely that the support for sudo-type chroots in sbuild is broken. I don't think anybody is using those anymore. If it turns out that you are still for some reason using the sudo backend, then I would like to help you investigate how to best fix it. Thanks! cheers, josch
signature.asc
Description: signature