[Logcheck-devel] Bug#515156: Same bug after removal + reinstall
martin f krafft
madduck at debian.org
Tue Aug 18 06:15:28 UTC 2009
also sprach Frédéric Brière <fbriere at fbriere.net> [2009.08.18.0129 +0200]:
> > 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
>
> The latter is not an option, since the logcheck user does not have an
> assigned UID. I've therefore applied the former solution.
I don't think this is the right solution. With
f573efec2645cd78dcc7ed5726106588f378acaa I removed the lock
directory from the package, but forgot the postinst stuff. This is
due to policy requiring /var/lock directories to be empty. Thus,
logcheck needs to create the lock directory at runtime (which it
does), and this is the place to fix the ownership and permissions.
--
.''`. martin f. krafft <madduck at d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
URL: <http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20090818/5e17e67b/attachment.pgp>
More information about the Logcheck-devel
mailing list