[buildd-tools-devel] Bug#838768: sbuild-createchroot should let me re-create an existing chroot/tarball

Johannes Schauer josch at debian.org
Thu Nov 10 08:04:27 UTC 2016


Control: tag -1 + moreinfo

Hi,

On Sat, 24 Sep 2016 17:38:17 +0200 Julien Cristau <jcristau at debian.org> wrote:
> On Sat, Sep 24, 2016 at 17:18:50 +0200, Julien Cristau wrote:
> > I want to be able to update a sbuild chroot by re-creating the tarball from
> > scratch, rather than running sbuild-update.  sbuild-createchroot used to
> > let me do that by creating a new tarball and deleting the new duplicate
> > config, but that doesn't seem to work anymore: chroot with name
> > sid-amd64-sbuild already exists at /usr/sbin/sbuild-createchroot line 214,
> > <$pipe> line 7.
> > 
> > Basically I'd like to have the opposite of --setup-only, where the
> > /etc/schroot/chroot.d is left unchanged, but I just get a newly-built
> > tarball.
> > 
> I managed to get the result I wanted with the --chroot-suffix option.

so... is there then still a bug?

I also note that there now exists sbuild-destroychroot which provides an easy
way to get rid of old chroots.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20161110/9fa2cad6/attachment.sig>


More information about the Buildd-tools-devel mailing list