Hi, On Sun, Jul 07, 2024 at 09:45:51AM GMT, Johannes Schauer Marin Rodrigues wrote: > I am not using the schroot backend and when I did in the past, I used it > exclusively with tarballs. You seem to be creating directory-based chroots for > schroot. This is nothing that I am using in my daily sbuild usage, which > probably explains why I'm not running into bugs like these. > > If you can supply a patch that does the right thing, that'd make me very > happy. > As I'm not using schroot anymore, my motivation to fix this is low but it'll > be > put on the TODO list.
I'd love to provide a patch, but I don't speak perl :-( Maybe a simple solution is to invoke sbuild-update instead of chrooting since it already do the proper setup. Actually I was just Ctrl-C and running sbuild-update afterwards. I acknowledge is a low priority thing. Actually I stopped adding gpg because I don't sign stuff in there. It was just documented in sbuild's wike page and that was the reason I was adding --include=gpg. > For anybody having a go at fixing the issue, maybe it would be best to use the > ChrootUnshare backend for $session instead of ChrootPlain. The code is run as > the superuser anyways. > > Thanks! > > cheers, josch Cheers, Charles
signature.asc
Description: PGP signature
