Bug#1068591: systemd-container: doesn't list a default package for default-dbus-system-bus dependency
Control: tags -1 wontfix Control: close -1 On Mon, 8 Apr 2024 09:21:32 +0200 =?UTF-8?Q?Rapha=C3=ABl_Halimi?= wrote: > Le 07/04/2024 à 19:34, Michael Biebl a écrit : > > As you correctly noticed, this is a bug/fault in debootstrap. > > I don't think individual packages should work around that, so I'm > > included to close this as wontfix (or reassign/merge to debootstrap). > > Fair enough, I understand. Do you want me to reassign it ? > > > Fwiw, you might use an alternative debootstrap tool like mmdebstrap > > which works properly in that regard. > > I didn't know about this tool. Thanks for the tip :) Yes this is a known debootstrap issue, and we don't want to workaround it here. Also, I am not sure the systemd-container package is actually needed _inside_ the container, as it provides tools and services to run containers _on the host_. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1068591: systemd-container: doesn't list a default package for default-dbus-system-bus dependency
Le 07/04/2024 à 19:34, Michael Biebl a écrit : As you correctly noticed, this is a bug/fault in debootstrap. I don't think individual packages should work around that, so I'm included to close this as wontfix (or reassign/merge to debootstrap). Fair enough, I understand. Do you want me to reassign it ? Fwiw, you might use an alternative debootstrap tool like mmdebstrap which works properly in that regard. I didn't know about this tool. Thanks for the tip :) Regards, -- Raphaël Halimi
Bug#1068591: systemd-container: doesn't list a default package for default-dbus-system-bus dependency
Am 07.04.24 um 18:19 schrieb Raphaël Halimi: Note 1: one could think that it's debootstrap's fault for not resolving dependencies on virtual packages; indeed, it has already been reported several times (#878961, merged with #827602 and #931760; as well as Launchpad #86536) unfortunately never fixed yet; but, IMHO, since systemd-container is usually needed in systemd-nspawn containers, and (except for the host) is usually installed via debootstrap, it makes it kind of a special case, in the sense that systemd (as a whole) should take care that systemd-nspawn containers can be built and started easily. As you correctly noticed, this is a bug/fault in debootstrap. I don't think individual packages should work around that, so I'm included to close this as wontfix (or reassign/merge to debootstrap). Fwiw, you might use an alternative debootstrap tool like mmdebstrap which works properly in that regard. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068591: systemd-container: doesn't list a default package for default-dbus-system-bus dependency
Package: systemd-container Version: 249.6-1 Severity: minor Dear developers, systemd-container lists "default-dbus-system-bus | dbus-system-bus" as a dependency. This is usually correct since APT is smart enough to resolve the dependency, but that's not the case with debootstrap. Since systemd-container is usually needed in systemd-nspawn containers, it should be installed at debootstrap time, but currently, running debootstrap with "--include=systemd-container" fails because no D-Bus implementation is pulled in as dependency. It used to work in versions older than 249.6-1 (before the dependency was changed from the real "dbus" package to "default-dbus-system-bus | dbus-system-bus" virtual packages, so it may qualify as a regression). Using "--include=systemd-container,dbus" (or dbus-broker) works. Could the real dbus package (since it's currently the default D-Bus implementation in Debian) be listed as an alternative dependency (and ideally, in bookworm too) ? Note 1: one could think that it's debootstrap's fault for not resolving dependencies on virtual packages; indeed, it has already been reported several times (#878961, merged with #827602 and #931760; as well as Launchpad #86536) unfortunately never fixed yet; but, IMHO, since systemd-container is usually needed in systemd-nspawn containers, and (except for the host) is usually installed via debootstrap, it makes it kind of a special case, in the sense that systemd (as a whole) should take care that systemd-nspawn containers can be built and started easily. Note 2: dbus-broker has the reputation of being better than dbus on various points, and could be considered as a clever choice for containers, but systemd-container currently lists "default-dbus-system-bus" as first alternative, which is provided by "dbus". Regards, -- Raphaël Halimi
