Control: retitle -1 gridsite: configuration files outside /etc Control: reopen -1 Control: severity -1 serious
On 2013-08-23 17:02, Mattias Ellert wrote: > They are handled by the normal configure file mechanism in dpkg, and the > md5sums are tracked in the package status, the same way it is for other > configuration files. > > $ dpkg --status gridsite > Package: gridsite > Status: install ok installed > [ ... ] > Conffiles: > /var/lib/gridsite/.gacl 88f4b45b6569fac47298439f2c911db5 > /var/lib/gridsite/gridsitefoot.txt 45ae35fb1a24a05bfbea36c3500ed5ba > /var/lib/gridsite/gridsitehead.txt 80aaad7a677d7bd24c8e7e7594befa06 > /etc/apache2/sites-available/gridsite.conf a7a43c456129084c6fb1c538e01ed0ae > /etc/apache2/mods-available/zgridsite.load 8841babc5836a6b0264cffd6b4be1582 > /etc/apache2/mods-available/zgridsite.conf 500abc73c2856aa23af9bf3a33f45caf > [ ... ] > > On package upgrade the files are managed correctly by dpkg. There is no > need for any additional managing using maintainer scripts. If the file > in the new package differs from the file in the old package the file is > replaced if the installed file has not been changed and otherwise not. > Which is the expected behaviour. > > I don't see where the bug is here. Then it's a violation of policy 10.7.2 http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files "Any configuration files created or used by your package must reside in /etc. [...]" Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
