Samuel Thibault, le ven. 11 juil. 2025 23:38:55 +0200, a ecrit:
> Helmut Grohne, le ven. 11 juil. 2025 23:30:37 +0200, a ecrit:
> > > If so, then the easier option would be to let sbuild create the tarball, 
> > > and
> > > not point it to the pbuilder tarball.
> > 
> > Yeah. That's what we ended up doing.
> 
> But I really like maintaining the state of my tarballs with pbuilder, so
> I'd really like sbuild to be able to use them.

More precisely, I *need* to tune my chroots in ways that sbuild doesn't
currently seem to support, and probably won't all support (not only
adding some repositories, but also other components, other suites,
possibly tune some configuration, etc.) so unless sbuild grows some
"login --save-after-login" support, I *have* to keep using pbuilder for
my various workflows while staying sane (it's *way* simpler to use a
shell to do what I need than use a flurry of options that I have to look
up in the sbuild manpage).

Samuel

Reply via email to