Control: severity -1 normal
Control: tags -1 + patch
Andreas Beckmann writes ("Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
> While the package works fine after a fresh install in sid or bookworm,
> the issue is still present after an upgra
Followup-For: Bug #1035361
Control: found -1 0.9.2
While the package works fine after a fresh install in sid or bookworm,
the issue is still present after an upgrade from bullseye to bookworm.
File permissions of conffiles do net seem to get updated on upgrades,
this needs to be fixed manually in
Control: clone -1 -2
Control: retitle -2 ancient chown syntax
Control: severity -2 serious
Andreas Beckmann writes ("Re: Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
> Setting up sauce (0.9.1) ...
> Checking for SAUCE databases i
Andreas Beckmann writes ("Re: Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
> [trying] it manually by installing logrotate and sauce in a chroot
> (without removing sauce again):
Ah!
Thanks for investigating. I think that I ought to fix
On 02/05/2023 11.37, Ian Jackson wrote:
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
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 noti
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
7 matches
Mail list logo
