Package: dh-systemd Version: 1.15 Severity: normal (This issue was reported on IRC by uau)
We generate mainterscripts code to mask services when a package is removed (and unmask them again on re-install). The reasoning for this behaviour is, that on remove the native service files are removed but the SysV init scripts (which typically are conffiles) aren't. Conffiles are only removed on purge. While typically SysV init scripts become no-ops if their corresponding binary has been removed, having the services show up in systemctl status, is confusing. When masking a service which should take into account, that the administrator has made local modification by copying the file to /etc/systemd/system. In this case we shouldn't try to overwrite this file with a /dev/null symlink. On re-install, we also need to make sure when running the unmask, to take into account that /etc/systemd/system/<unit> is a file (custom modification) and not remove it in that case. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dh-systemd depends on: ii debhelper 9.20131227 ii perl 5.18.2-2 dh-systemd recommends no packages. dh-systemd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
