[Pkg-systemd-maintainers] Bug#619244: Bug#619244: Bug#619244: systemd: unowned files after purge (policy 6.8, 10.8): /etc/machine-id

Michael Biebl biebl at debian.org
Mon Apr 14 22:12:39 BST 2014


Am 14.04.2014 14:22, schrieb Michael Stapelberg:
> Hi coldtobi,
> 
> coldtobi <tobi at coldtobi.de> writes:
>> Maybe new imput:
>> On drizzle I had the same issue with database files.
>> My solution was to ask the user (debconf) if the files should be removed on
>> purge, and defaulted that to yes. This is compliant with the policy and you can
>> still explain why this file is needed and why systemd suggests to keep the
>> file. 
> I don’t think this is a good idea. Users should not be bothered with
> technical details such as this just for following the policy to the word.

I agree. I don't want to add a debconf prompt for this. Aside from the
overhead, this just shifts the problem to the user.

>> BTW, *why* does systemd needs this file to be constant? Google did not have an
>> answer for me... Do you have a pointer? I only found a reference that it can be
>> regenerated on stateless systems, so out of this I assume things will not break
>> if someone purges systemd and later reinstall it.
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619244#45
> 
>> (Please note that this bug has a huge impact on piuparts testing, as all
>> packages directly and indirectly depending on systemd will not be tested until
>> this is fixed policy-like)
> Then please work on fixing it…? :)
> 
> I think the best option (as discussed in this bug already) is to move
> the file to a more central package like base-files.

Fwiw, I wouldn't mind to unconditionally rm the file on purge in postrm
(we do the same for dbus wrt /var/lib/dbus/machine-id) given that no
other package relies on the file.

That said, I don't know if any other package relies on /etc/machine-id.
I do know that dbus makes use of it but I dunno all the details
regarding the /var/lib/dbus/machine-id fallback

Say we first install systemd, which generates /etc/machine-id, then
later dbus. Will in this case a /var/lib/dbus/machine-id file be created
or will dbus use /etc/machine-id?
In this case we can't remove /etc/machine-id again, as it would break
dbus, unless dbus would on-the-fly generate a /var/lib/dbus/machine-id
if no /etc/machine-id is available.

Maybe Simon knows more.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

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


More information about the Pkg-systemd-maintainers mailing list