Bug#950684: systemd: upgrade fails in a chroot where /var/log/ owner is not root:root

Michael Biebl biebl at debian.org
Wed Feb 5 12:22:28 GMT 2020


Am 05.02.20 um 10:47 schrieb Andrey Rahmatullin:
> Attached.


> Running create action for entry a /var/log/journal
> Detected unsafe path transition /var/log → /var/log/journal during canonicalization of /var/log/journal.
> Running create action for entry a /var/log/journal

It appears this problem happens, if / is not owned by root:root and
doesn't have 755. Since you said that all your files/directories were
owned by sbuild:sbuild, it is likely that those messed up permissions
tripped up systemd-tmpfiles.

Tbh, I'm not sure if it's worth fixing. A chroot like this appears to be
severly misconfigured unless someone can provide a good reason sbuild is
doing this.

Regards,
Michael


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200205/a5723051/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list