Your message dated Sat, 1 Feb 2025 22:26:52 +0100
with message-id
<picdl4igzjadeauxb3l757oodtglu5cal6sr3n3g5uctsme...@tarta.nabijaczleweli.xyz>
and subject line Close: Bug#604812: Duplicate logrotate files at dist-upgrade.
has caused the Debian Bug report #604812,
regarding Duplicate logrotate files at dist-upgrade.
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 [email protected]
immediately.)
--
604812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604812
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: webfs
Version: 1.21+ds1-6
Severity: important
The stable version 1.21-5.1 of Webfs, as an effect of executing
the postinst script, manually contructed a file for drop-in as
/etc/logrotate/webfsd
The updated package, starting with 1.21+ds1-1, is using
dh_installlogrotate to register a pre-fabricated file as
/etc/logrotate/webfs
Observe that the file name differs, and that the new name is
identical to the package name, thus ought to have precedence.
The end effect of this is that the daily logrotate task will
complain about duplicate log entries, should the administrator
of the old package have specified
/var/log/webfs/webfs.log
as his intended logging file. The "stable" postinst used a dynamic
evaluation of "/etc/webfs.conf", or its template, to determine the
name of the file to rotate. Since the reformed packaging "1.21+ds1"
is using this latter path as pre-coded location for the logrotate
description, and since the old packaging clearly expected the same
name as the natural choice, it is only in this single case that the
clash becomes visible.
--- End Message ---
--- Begin Message ---
This effected a transition during the squeeze release cycle,
so all systems were either fixed manually or have never experienced this.
Attempting a fix 15 years later is counter-productive.
signature.asc
Description: PGP signature
--- End Message ---
