[Logcheck-devel] Bug#515156: Same bug after removal + reinstall

Karl E. Jorgensen karl at jorgensen.org.uk
Tue Apr 7 09:52:11 UTC 2009


I ran into the same problem after somebody uninstalled logcheck and I
re-installed it.

It turned out that the ownership of /var/lock/logcheck where root:root -
sudo chown logcheck:logcheck /var/lock/logcheck solved it.

I see that there already is a check for the permissions in the postinst
which (as far as I can see) *should* have fixed the permissions and
ownership there.

When re-installing the logcheck package (which was previously removed,
but not purged), dpkg will pass the version number of the most recently
configured version [1] - which in this case would be 1.2.69. And since
1.2.69 >= 1.2.39, the chown+chmod in postinst is bypassed...

I think that /var/lock/logcheck becamed owned by root:root upon
reinstallation, as the .deb ships with it as root:root (but I have not
been able to verify that).

I think it would be sensible to do one (or both?) of:
* chown+chmod unconditionally in postinst
* make the ownership of /var/lock/logcheck logcheck:logcheck in the .deb

Hope this helps

[1]
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-configdetails
-- 
Karl E. Jørgensen
http://www.jorgensen.org.uk
http://karl.jorgensen.com





More information about the Logcheck-devel mailing list