Your message dated Thu, 09 Jan 2014 21:20:17 +0000 with message-id <e1w1n1v-00047g...@franck.debian.org> and subject line Bug#734784: fixed in snapper 0.1.8-2 has caused the Debian Bug report #734784, regarding libpam-snapper: leaves modified pam configuration after package removal 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.) -- 734784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libpam-snapper Version: 0.1.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts 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. 0m27.7s ERROR: FAIL: After purging files have been modified: /etc/pam.d/common-session not owned /var/lib/pam/seen not owned /var/lib/pam/session not owned This looks like pam-auth-update is not called properly during package removal. cheers, Andreaslibpam-snapper_0.1.8-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---Source: snapper Source-Version: 0.1.8-2 We believe that the bug you reported is fixed in the latest version of snapper, 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 734...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Dandrimont <ol...@debian.org> (supplier of updated snapper 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...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 09 Jan 2014 21:41:31 +0100 Source: snapper Binary: snapper libsnapper2 libsnapper-dev libpam-snapper Architecture: source amd64 Version: 0.1.8-2 Distribution: unstable Urgency: medium Maintainer: Nicolas Dandrimont <ol...@debian.org> Changed-By: Nicolas Dandrimont <ol...@debian.org> Description: libpam-snapper - PAM module for Linux filesystem snapshot management tool libsnapper-dev - Library for Linux filesystem snapshot management tool (header fil libsnapper2 - Library for Linux filesystem snapshot management tool snapper - Linux filesystem snapshot management tool Closes: 734784 Changes: snapper (0.1.8-2) unstable; urgency=medium . * Move PAM config to /usr/share/pam-configs/snapper for consistency with other pam module-providing packages (Closes: #734784) Checksums-Sha1: f1be2071b7cbd07e6b237b01fa4ee71f2feede2c 2123 snapper_0.1.8-2.dsc 9472ce5c1fc2b28927b0b979cda7f8145960fe22 5577 snapper_0.1.8-2.debian.tar.gz f0dccbb64c6dd56769db3b543d4655f3fe6c8357 161816 snapper_0.1.8-2_amd64.deb 7cbc084f83237531377cddab7f1cb46cc8a0baad 184196 libsnapper2_0.1.8-2_amd64.deb 88e902fc7f201f8f76c498ad15ae80bd08265e9d 36920 libsnapper-dev_0.1.8-2_amd64.deb 023fddf7627181b7241246665739cdb6691b4e1e 10284 libpam-snapper_0.1.8-2_amd64.deb Checksums-Sha256: b46acda534a840c4bfbd5eca67288c537789c54ab7536b5ba0d4776c84e3c611 2123 snapper_0.1.8-2.dsc e79f92143d695a5e62cfcd14d0af63ce977306ef6abd852ff42f0aff2aec6551 5577 snapper_0.1.8-2.debian.tar.gz bcda0d928835ae2822b4393fea423c6fe4fdea1cb468865151f168f9e38fa260 161816 snapper_0.1.8-2_amd64.deb fb71382a26dfcadfb5fb6065d038945291f0ef19891b035e14cba9621a20bbd5 184196 libsnapper2_0.1.8-2_amd64.deb 783c19211e4425436a542795e86c755a83ed2bbfdc9e1eb75b63f3c0c6002318 36920 libsnapper-dev_0.1.8-2_amd64.deb 3c1443edbace083196c1d783a9e11462b76090f7e88c20dba848294f8a85f81e 10284 libpam-snapper_0.1.8-2_amd64.deb Files: b1cd12afce2cd24368dbef29ad2d2884 2123 utils optional snapper_0.1.8-2.dsc ef38c25f237a2daec68c10c2b4dc1b73 5577 utils optional snapper_0.1.8-2.debian.tar.gz 68a1f1b2e1ae739c55d8415361ffaa07 161816 utils optional snapper_0.1.8-2_amd64.deb fa4b93ea6d9843070c43da19c030f3c7 184196 libs optional libsnapper2_0.1.8-2_amd64.deb 092906ddf1b1c2cbb652fcf862b1e55a 36920 libdevel optional libsnapper-dev_0.1.8-2_amd64.deb 1fd5299202538ae064347799eb3d165a 10284 admin optional libpam-snapper_0.1.8-2_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJSzwtiAAoJEOwFizKNvp3qW0EQAKl66be8oAvdADpcXapj6n3w WgDom32r8myGbaGZ4ZiROyBgQYKkRzJS1ULNwkTgd2gxvG0P/BPOls8SQvTm4Apx CtX6PteGvDyefOT7PqhA6k6ZdIRCJWGBZqqvBg4pgsO1pjAf6cayhdRZgIgfAtHH 8JEIFeEnxLQsg91ArA6T59r4Rcz6RwtwXfG75XmhwvW/sTUmCu2S5ZWZQHNedmYI C+35FKQlLa/cLJYixaTsTFCkeLYNLcIuLygwZUtn9LX9Hg0L39Wy1MtPFWtNcfnE ZHvaPnojwvYf5r+fgDW/qHOBYHiTJw0cLAh1qXx+zyuEVxsVufCU+F8IUUa4aII6 cKfEnNJnIOhtxlymF3PRN+FxASZqxCwdA77vouJNJk/b1GOlS8RCKDA0owwNtxZ8 x3CDrQKTMZXy4+OzOo48Ah+nrb7HqA7CJxXCOejnh5MjCq7l5KzDoOpc0i5xxqZY 3Qe/WmvAvM3FUx9tHmy1bvMc189NjdK5kXysdRbjnQRnPNZSfWlIdiXEOg7FfB87 HRUatCTt1qmo9fwZT0fSVRAb5mg+61EnpBc8HfPg+htV5awbfPsfmxqxEvpe+5HF rMJHrL0XjC/Sz3/0ifJ9YQWDrNXQvQS6NwTE/ux3yMbE9si3xLmn4BGyYk9irUdv BPABG46wg1eY1E9Pc0G+ =7Y8S -----END PGP SIGNATURE-----
--- End Message ---