Re: rmdir: failed to remove '/var/lock': Directory not empty

[Bo YU <tsu.yubo@gmail.com>]

Hi,
On Wed, May 11, 2022 at 04:01:52PM +0200, Johannes Schauer Marin Rodrigues wrote:
> Hi,
>
> Quoting Bo YU (2022-05-11 15:49:17)
...
> this is not a problem with sbuild or with libreoffice. From your log it seems
> that the base-files package wasn't installed in your chroot before. This means
> that the following line from the base-files postinst will be executed:
>
> https://sources.debian.org/src/base-files/12.2/debian/postinst.in/#L78
>
> Usually, that conditional only get executed when you run debootstrap or
> mmdebstrap because only in those scenarios should it happen that an
> Essential:yes package is not installed yet. In your case, your chroot was
> missing an Essential:yes package (base-files) and sbuild tried to install it
> which failed because your chroot was already set up and thus had files in
> /var/lock.
>
> You should be able to solve this problem by using a chroot that contains all
> Essential:yes packages. How did you even create one without all of them?

Thanks for your explanations. I created chroot with below:
```
sudo sbuild-createchroot --arch=riscv64 --foreign  --keyring="" \
--include=debian-ports-archive-keyring --make-sbuild-tarball=/srv/sid-riscv64-sbuild.tgz \
sid /tmp/chroots/sid-riscv64-sbuild/  http://ftp.ports.debian.org/debian-ports/
```
Maybe one of these parameters prevents some essential packages from being installed.
And I happened to miss to execute `sbuild-update -ud sid-riscv64-sbuild` to check
the dependency integrity of the chroot.

It is easy to fix it as you said. I entered into the chroot with `sbuild-shell` and
installing necessary packages by manual and to execute `sbuild-update` again.
That is ok.

Thank you again.

BR,
Bo

> Thanks!
>
> cheers, josch