Bug#1108542: openssh-server: Debian Trixie: bad dependancy with systemd*
Jean-Marc LACROIX <[email protected]>
| Newsgroups | gmane.linux.debian.devel.ssh |
|---|---|
| Message-ID | <f09619f0-cbda-43c6-8439-4c8748fd7d39__39281.7828267411$1753609519$gmane$org@free.fr> |
Le 30/06/2025 à 22:50, Colin Watson a écrit : > On Mon, Jun 30, 2025 at 10:41:15PM +0200, Jean-Marc LACROIX wrote: >> It seems that on package openssh-server, there is now one dependency >> with systemd on Debian Trixie (release 13). >> >> This feature is not compatible with one target running sysvinit-core >> in place of systemd. > [...] >> REMOVING: >> openssh-server* systemd-standalone-sysusers* > > But: > > Package: systemd-standalone-sysusers > Description: standalone sysusers binary for use in non-systemd systems > Standalone sysusers binary with minimal dependencies. > This package conflicts with the main systemd package and is meant for > use in > non-systemd systems. > > Is this actually a problem for any reason other than you having removed > everything matching "systemd*"? As indicated, this particular package > should be fine even if you're running sysvinit. > > An alternative, if you so wish, is to install the opensysusers package > instead. openssh-server's dependencies allow that (since it Provides: > systemd-sysusers). > Hello Colin, Thank you very much for your suggestion to never remove systemd*. I've added the exact list of dedicated "systemd" packages, making it easier to manage, to my Ansible YAML list. It works perfectly. For my own understanding, could you confirm that "systemd-standalone-sysusers" is a recent Debian package, built on Debian Bookworm , and not available on old Debian release. (< 9). Therefore, i must make some trivial code to manage this feature on old Debian release ? Thanks to close this bug at now. Best regards