[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

configuration files, ownership and dpkg-statoverride


I am looking into dbconfig-common RC bug 720517 [1] and I was wondering
what the general idea is of maintainer scripts changing the permissions
and/or owners of configuration files and the use of dpkg-statoverride. I
myself find it unacceptable that updating a package changes the
permissions/owners of a configuration file without asking, even when I
have not documented that fact with dpkg-statoverride. At least that is
how I read policy 10.7.3 [2].

Do other people find it sensible that you need to document this fact
with dpkg-statoverride? In other words, is it ok to change permissions
and ownership as done by dbconfig-common if you didn't?


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720517
[2] https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: