Package: kdump-tools Version: 1:1.6.2-1 Severity: normal systemd 234 breaks any dependencies of default.target. So kdump-tools would not be started when used with that systemd version. That affects Ubuntu Artful, for example. [0]
Though that systemd issue has been fixed on systemd 235, when reading the discussion upstream [1] [2], I have the impression that generally using an aliased target is not a good idea. Also, as Steve Langasek has pointed out, the default target may be a different one that we do not expect, and loading kdump and all its dependencies may not be a good idea. Using multi-user.target by default will work on both graphical and non-graphical systems, and is a good default. If the user wants to enable kdump-tools on a different target, one may still do so. [0] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708409 [1] https://github.com/systemd/systemd/issues/6334 [2] https://github.com/systemd/systemd/issues/5248 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdump-tools depends on: ii bsdmainutils 9.0.14 ii debconf [debconf-2.0] 1.5.65 ii file 1:5.32-1 ii kexec-tools 1:2.0.15-1 ii lsb-base 9.20170808 ii makedumpfile 1:1.6.2-1 ii ucf 3.0036 kdump-tools recommends no packages. kdump-tools suggests no packages. -- Configuration Files: /etc/default/kdump-tools changed [not included] -- debconf information excluded