Bug#950684: systemd: upgrade fails in a chroot where /var/log/ owner is not root:root
Michael Biebl
biebl at debian.org
Fri Feb 7 18:10:40 GMT 2020
Am 05.02.20 um 18:26 schrieb Andrey Rahmatullin:
> On Wed, Feb 05, 2020 at 06:15:34PM +0100, Michael Biebl wrote:
>> Now, the question: How should systemd postinst behave in this case?
> I think failing is fine. I'd ask the sbuild maintainers what do they think
> about this situation, and why such chroots exist (and/or maybe ask some
> other people if theis chroots have the same perms).
I asked Johannes. He is not aware or remembers any such issue.
My proposal would be to keep this bug report open for a while. If we
have other users running into this issue and commenting on this bug
report, we might consider looking for a workaround.
Otherwise I'll probably just going to keep the current status quo.
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/20200207/10ac98d6/attachment-0001.sig>
More information about the Pkg-systemd-maintainers
mailing list