Your message dated Wed, 14 Nov 2012 21:47:27 +0000 with message-id <e1tyknv-0008ux...@franck.debian.org> and subject line Bug#688377: fixed in ferm 2.1.1-2 has caused the Debian Bug report #688377, regarding ferm: modifies conffiles (policy 10.7.3): /etc/default/ferm to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 688377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: ferm Version: 2.1-2 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 2.0.7-1 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/ferm cheers, Andreas
ferm_2.1-2.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---Source: ferm Source-Version: 2.1.1-2 We believe that the bug you reported is fixed in the latest version of ferm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 688...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Wirt <formo...@debian.org> (supplier of updated ferm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Thu, 01 Nov 2012 19:28:58 +0100 Source: ferm Binary: ferm Architecture: source all Version: 2.1.1-2 Distribution: experimental Urgency: low Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt <formo...@debian.org> Description: ferm - maintain and setup complicated firewall rules Closes: 688377 Changes: ferm (2.1.1-2) experimental; urgency=low . [ Salvatore Bonaccorso ] * Fix "ferm: modifies conffiles (policy 10.7.3): /etc/default/ferm" (Closes: #688377) - Don't install ferm.default as conffile in /etc/default - Read /etc/default/ferm in ferm.config. If /etc/default/ferm exists and ENABLED= is present then store the value of ENABLED into debconf db. - Create /etc/default/ferm in postinst. Create /etc/default/ferm if it does not yet exists in postinst. Furthermore if the admin deleted or commented the ENABLED then (re-)add it to the configuration file in postinst. - Remove configuration file on purge in postrm script Checksums-Sha1: 2e85412d41b2f1ccba7d9db568291331116be0ff 1137 ferm_2.1.1-2.dsc 4cb127b77dac0ae76f5d1cc5cc9a5a7c4e7b8831 15382 ferm_2.1.1-2.diff.gz 8de88b859f253987db893bc78b016e0089e9e9da 111566 ferm_2.1.1-2_all.deb Checksums-Sha256: 4572a8349b451ad1fb121818901cd397003e68d4a0e62959dc969c36d4856898 1137 ferm_2.1.1-2.dsc 0ab4f5f33e9be65a2f043be73e605a0053e315127da5e50dd81ca1af71cb436e 15382 ferm_2.1.1-2.diff.gz 8e61b83e79bf01a4d43662a9b747e38631f1da374809526e4b662622781288f5 111566 ferm_2.1.1-2_all.deb Files: d4c0d9aad32e7abee98b7d0e1aee222f 1137 net optional ferm_2.1.1-2.dsc ea34449b9b60b20f5825a7bc47f8404d 15382 net optional ferm_2.1.1-2.diff.gz 899901ca0993a72ad6cb35675bd13822 111566 net optional ferm_2.1.1-2_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlCkDjoACgkQ01u8mbx9Agq6WACfQegyPiAx+Dl1//+ps6Tfp9F1 FU0An1lc24bblxoxWLO9Vaf8L9T/Xkjf =41qf -----END PGP SIGNATURE-----
--- End Message ---
