Control: forcemerge 421344 -1 Hi!
On Tue, 2012-10-09 at 16:12:16 +0200, Andreas Beckmann wrote: > Package: dpkg > Version: 1.16.8 > Severity: important > User: [email protected] > Usertags: piuparts > Control: affects -1 syslog-ng-core > the syslog-ng-core is one of the few packages using symlink conffiles, > causing trouble for piuparts and debsums because dpkg does not properly > handle this. There are several other issues with symlink-conffiles, but > none seemed to match this. symlink conffiles have never been supported, packages using that are buggy and should be fixed (see also 421344 and 312846). > The following files are shipped by the syslog-ng-core package in sid: > lrwxrwxrwx 1 root root 37 Oct 3 15:49 > /etc/systemd/system/multi-user.target.wants/syslog-ng.service -> > /lib/systemd/system/syslog-ng.service > lrwxrwxrwx 1 root root 37 Oct 3 15:49 /etc/systemd/system/syslog.service -> > /lib/systemd/system/syslog-ng.service > -rw-r--r-- 1 root root 251 Oct 3 15:49 /lib/systemd/system/syslog-ng.service I guess there's something to be said about symlinked configuration shipped in /lib, but in any case the above is just wrong and goes against the current system. > The symlinks in /etc/ are conffiles. > > And syslog-ng.service is having these md5sums: > 3933398f3e6cf91d25e515977876208b /lib/systemd/system/syslog-ng.service <== > 3.3.6-1, sid > 41541800d349863ddd9f4279211ec4b3 /lib/systemd/system/syslog-ng.service <== > 3.3.5-2, wheezy > The md5sum for the symlink-conffiles does not get updated during package > upgrades - the link itself does not change, but the link target (that > was hashed and is not a conffile in this example) has been updated. > And of course debsums claims there are modified conffiles ... Well, once this is natively supported by dpkg, what would be stored would be the target of the symlink not its hash. The conffile prompt interface would need to be adapted to show the difference in symlink targets, etc. thanks, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
