[buildd-tools-devel] Bug#801572: Bug#801572: sbuild-update -u not saved

[Johannes Schauer]

Hi,

On Tue, 13 Oct 2015 10:31:11 +0200 Gaudenz Steinlin <gaudenz at debian.org> wrote:
> Raphael Hertzog <hertzog at debian.org> writes:
> > The correct command to use was always “sbuild-update [options]
> > source:sid-amd64-sbuild”.
> >
> > At least that's my understanding and what my own chroot update scripts
> > have been doing for ages.
> 
> I just ran into the same problem and this does not solve it. Attached is the
> debug output (std output and error) from running sbuild-update with the
> following command:
> /usr/bin/sbuild-update -u source:sid-amd64 --debug
>                           ^^^^^^

This problem is a regression.

You should not need to prefix your chroot name with "source:" because
sbuild-update already does that for you. It would not make sense to update
anything else than the source for sbuild-update.

> This used to work in the past even without the explicit "source:" qualifier.
> But it should at least work with it.

Correct. I now did an upload that fixes this regression to unstable.

It is now again possible to just run:

	$ sudo sbuild-update -udcar unstable-amd64-sbuild

Thanks!

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