Andreas Beckmann <deb...@abeckmann.de> writes: >>From the attached log (scroll to the bottom...): > > 0m21.7s ERROR: WARN: Broken symlinks: > /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service > /etc/systemd/system/multi-user.target.wants/syslog-ng.service -> > /lib/systemd/system/syslog-ng.service > > 0m23.1s ERROR: FAIL: Package purging left files on system: > /etc/systemd/ owned by: syslog-ng-core > /etc/systemd/system/ owned by: syslog-ng-core > /etc/systemd/system/multi-user.target.wants/ owned by: > syslog-ng-core > /etc/systemd/system/multi-user.target.wants/syslog-ng.service -> > /lib/systemd/system/syslog-ng.service owned by: syslog-ng-core > /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service > owned by: syslog-ng-core
*grumble* It appears dpkg does not purge symlink conffiles. We'll have to do that in the postrm ourselves. Might revisit the whole systemd-override-is-a-conffile thing too, while there: create the symlinks if not present. We can leave advanced stuff life diffing and warning the user if there were changes in the /lib file until a systemd hits unstable that has the systemd-delta tool, and we have a common way to do this kind of thing. But then... it might be better if we stick with the conffiles. Anyway, thanks for the report! -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
