Your message dated Sat, 20 May 2023 19:59:09 +0200 with message-id <afeb8f96-2c8c-87e1-0450-5c6ec86c9...@debian.org> and subject line Re: SAUCE RC bugs to be fixed for bookworm has caused the Debian Bug report #1035361, regarding sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755 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.) -- 1035361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Version: 0.9.2 The "c" in closes was missing in the changelog.
--- End Message ---