devuan-jessie-netboot-i386-alpha2.iso installer pulls in systemd
Bug description:
A minimal base system install pulls in systemd packages for no apparent reason .
Steps to reproduce:
- boot pristine VirtualBox VM using devuan-jessie-netboot-i386-alpha2.iso
- make only necessary configurations (language, location, locale, keymap)
- go with the defaults for everything else
- in "Software selection" un-check all options, to get a minimal install
- let installation finish
- boot into the new system
Observations:
systemd and libsystemd0 packages are installed:
~# apt --installed list | grep systemd
libsystemd0/stable,now 215-17 i386 [installed]
systemd/stable,now 215-17 i386 [installed]however, nothing seems to depend on it:
~# apt-cache --no-breaks --installed rdepends systemd
systemd
Reverse Depends:
~# apt-cache --no-breaks --installed rdepends libsystemd0
libsystemd0
Reverse Depends:
systemdboth packages can apparently be safely removed:
~# apt-get purge libsystemd0
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
libsystemd0* systemd*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 12.4 MB disk space will be freed.
Do you want to continue? [Y/n]
Removing systemd (215-17) ...
Purging configuration files for systemd (215-17) ...
Removing libsystemd0:i386 (215-17) ...
Purging configuration files for libsystemd0:i386 (215-17) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for libc-bin (2.19-18) ...Followup:
Thanks to Dan I was able to monitor the install process more closely and grabbed the installer syslog (attached). The problem might actually stem from the order of pre-depends alternatives in the init meta-package:
Jun 2 13:24:27 debootstrap: Selecting previously unselected package init.
Jun 2 13:24:27 debootstrap: Preparing to unpack .../archives/init_1.22_i386.deb ...
Jun 2 13:24:27 debootstrap: dpkg: regarding .../archives/init_1.22_i386.deb containing init, pre-dependency problem:
Jun 2 13:24:27 debootstrap: init pre-depends on systemd-sysv | sysvinit-core | upstart
Jun 2 13:24:27 debootstrap: systemd-sysv is not installed.
Jun 2 13:24:27 debootstrap: sysvinit-core is not installed.
Jun 2 13:24:27 debootstrap: upstart is not installed.Now systemd-sysv gets installed, and with it systemd et al.:
Jun 2 13:24:33 debootstrap: Selecting previously unselected package systemd-sysv.
Jun 2 13:24:33 debootstrap: dpkg: regarding .../systemd-sysv_215-17_i386.deb containing systemd-sysv, pre-dependency problem:
Jun 2 13:24:33 debootstrap: systemd-sysv pre-depends on systemd
Jun 2 13:24:33 debootstrap: systemd is unpacked, but has never been configured.Later, sysvinit-core replaces systemd-sysv:
Jun 2 13:24:46 debootstrap: dpkg: considering removing systemd-sysv in favour of sysvinit-core ...
Jun 2 13:24:46 debootstrap: dpkg: yes, will remove systemd-sysv in favour of sysvinit-coreBut the now dangling [lib]systemd[0] packages are never removed!
-
Both should be installed, with sysvinit as PID 1. The systemd package is required for stuff like logind.
-
Why would one want any of these on a bare base system install? Granted, if a user is absolutely positive that she wants some DE/DM combo that requires logind (gdm|mdm and gnome?), that would make sense. But then it gets pulled in anyway. And once a standalone logind is available, that would make the whole point moot, wouldn't it?
-
You need udev, it's a critical daemon. Also, almost the entire systemd is stuffed in one package (called "systemd"), so stuff that depend on logind pull in that package.
Edited -
Non sequitur. Udev in Jessie does not need systemd at all. And, as I understood, Devuan is not going with an systemd-ified udev for release, and possibly not with udev at all. If stuff depends on systemd, it has to made independent of it. Otherwise, what's the point in forking Debian and having Devuan after all? Just because of the PID1 thing? Sounds wrong to me. YMMV.
-
This is not strictly a d-i bug. We need to find out what packages are depending on it and fix them.
-
Also we are working on adding overrides to the repository to demote systemd so it isn't pulled in automatically on install. Probably will set it a priority of extra.
Edited -
ACK, it just manifests in d-i because that's the first (and usually only) time init gets installed from scratch. Avoiding systemd-sysv at that stage should already help to obtain a clean base system. When I find the time I will install a full-blown Xfce desktop with bells and whistles and compile a list which of the packages involved tend to gratuitously pull in systemd components.
-
fixed a while ago. Not specifically debian-installers fault.
-
Status changed to closed