Andreas Beckmann writes ("Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755"): > Package: sauce > Version: 0.9.1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts ... > 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.
Thanks for the report. I will fix this ASAP. > Usually the solution is to specify 'missingok' in the logrotate > configuration. I will do some tests but that sounds like a possible approach. > 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. I looked through the changelog and didn't find anything about missing logfiles since at least 2015. Are you sure ? > >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 I have one question. The message here is complaining about the file permission. I think that mode is probably wrong, but I don't think it is *dangerous*. I don't think I ought to change the mode for bookworm. Thanks, Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.