Hi, Mike Hommey <mh+reportbug@glandium.org> (2018-01-29): > Package: debootstrap > Version: 1.0.89 > Severity: normal > > Dear Maintainer, > > I was running sbuild-createchroot, and it failed with: > I: Chosen extractor for .deb packages: dpkg-deb > I: Extracting libacl1... > E: Error running debootstrap at /usr/sbin/sbuild-createchroot line 268. > > Turns out that was happening because the target directory existed and > was not empty. It seems to me sbuild-createchroot should know better and warn upfront. There are various cases where it makes sense for debootstrap to operate on the same directory (e.g. bootstrapping). > But neither debootstrap nor sbuild-createchroot printed out something > useful. Debootstrap surely shouldn't fail without saying what went Details are available in $target/debootstrap/debootstrap.log But yeah, I suppose we could point at it when a failure is returned by debootstrap. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature