On 2012-09-13 17:16, Niels Thykier wrote: > Please consider adding a check for files being modified by a > maintainer script. For an actual case of a package triggering this > issue, please see bdii/5.2.12-2 (bug #687534).
Can be solved by two custom scripts: one (post_install) that installs debsums, one (pre_remove) that runs it: 8m24.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpnBrq64', 'tmp/scripts/pre_remove_80_debsums'] 8m29.3s DUMP: debsums: no md5sums for mawk /etc/bdii/bdii-slapd.conf 8m29.3s ERROR: Command failed (status=2): ['chroot', '/tmp/piupartss/tmpnBrq64', 'tmp/scripts/pre_remove_80_debsums'] That was on squeeze ... Andreas Note: * installing debsums in pre_remove would require manual tracking + removing of the packages added * running debsums in post_install is bad for upgrade tests: we only want to check after the *last* install/upgrade, not after the *first* (or every) install - the newer versions might do proper cleanup of earlier mistakes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
