Package: sauce Version: 0.9.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package's logrotate configuration causes logrotate to exit with an error after the package has been removed (*) or when logrote is run but no logfile exists. Usually the solution is to specify 'missingok' in the logrotate configuration. *) logrotate configuration files remain installed and executed after a package has been removed, they only get removed when the package is purged. >From the attached log (scroll to the bottom...): 0m17.0s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate', '/etc/logrotate.d/sauce'] 0m17.0s DUMP: warning: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755 0m17.0s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate', '/etc/logrotate.d/sauce'] 0m17.0s ERROR: FAIL: Logrotate file /etc/logrotate.d/sauce exits with error or has output with package removed Setting severity to serious since this does not seem limited to being emitted after package removal but always. The current logrotate version in sid seems to be more strict. cheers, Andreas
sauce_0.9.1.log.gz
Description: application/gzip
