Johannes Schauer <jo...@debian.org> writes:

> Hi,
>
> Quoting Daniel Dehennin (2018-09-22 19:52:55)
>> I'm trying to setup an LVM schroot but I got the following error:
>> 
>> #+begin_src
>> /srv/chroot/sid-amd64-sbuild is not empty at /usr/bin/sbuild-createchroot 
>> line 279, <PH> line 13.
>> #+end_src
>> 
>> The problem is that sbuild-createchroot check for 3 directory entries without
>> taking “lost+found” as an exception.
>
> the reason why sbuild requires an empty target directory, are debootstrap bugs
> like these that make you loose everything in case a wrong code path is taken:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833525
>
> Now imagine that you actually had some previously recovered files in
> lost+found. If you are unlucky, those would then be deleted by a faulty
> debootstrap.
>
> Why don't you just rmdir the directory? Then you also made sure that there is
> indeed nothing inside that you still need. fsck will re-create it in case it
> needs it.

Thanks for the explanation, I already add a rmdir of “lost+found” as a
workaround.

You can considere this report closed.

Have a good day.
-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF

Attachment: signature.asc
Description: PGP signature

Reply via email to