Control: found -1 sbuild/0.72.0-2 Control: tags -1 - moreinfo On 24-Sep-2016, 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. I get the same behaviour: ===== $ sudo rm /etc/sbuild/chroot/unstable-amd64-sbuild rm: cannot remove '/etc/sbuild/chroot/unstable-amd64-sbuild': No such file or directory $ sudo rm -r /srv/chroot/unstable-amd64-sbuild/ rm: cannot remove '/srv/chroot/unstable-amd64-sbuild/': No such file or directory $ sudo sbuild-createchroot unstable /srv/chroot/unstable-amd64-sbuild/ http://httpredir.debian.org/debian/ chroot with name unstable-amd64-sbuild already exists at /usr/sbin/sbuild-createchroot line 214, <$pipe> line 1. ===== On 10-Nov-2016, Johannes Schauer wrote: > so... is there then still a bug? The bug in the above behaviour is: * The obvious filesystem entries where the chroot might “already exist” do not actually exist, yet the tool refuses with the above message anyway. * The user needs to make a decision about how to resolve the problem, but the message gives no help in finding what problematic thing “already exists”. Both those, IMO, need to be correct to resolve this bug. -- \ “I took a course in speed waiting. Now I can wait an hour in | `\ only ten minutes.” —Steven Wright | _o__) | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
