Debian network-manager: Please restore removed init script

Post by dane-pgp » Wed, Sep 16, 2020, 5:39 PM UTC

tremon wrote: post #33

pabs3 wrote: post #25

Earlier quoted context omitted.

> dbus hard depends on systemd That doesn't seem to be the case, the dbus package only depends on libsystemd0 and installing dbus in a clean chroot doesn't pull in systemd. $ apt-cache show dbus | grep Depends | grep -o ...systemd. | sort -u libsystemd0

just FYI, aptitude can identify the dependency chain between two packages. I don't know if it always finds the shortest chain, the most direct chain (choosing Depends over Recommends over Suggests), or just any chain, but on this machine (Ubuntu Xenial, the only one I can access right now): $ aptitude why network-manager systemd p network-manager Depends libpam-systemd i libpam-systemd Depends systemd (= 229-4ubuntu2…

Post by grifferz » Wed, Sep 16, 2020, 8:37 PM UTC

rektide wrote: post #42

grifferz wrote: post #2

I submitted this as being interesting because I feel it is a turning point in Debian's long init wars. The most recent Debian General Resolution on init support said something like "we chose systemd but compatibility with other inits is important" It did not clarify whether a package maintainer was allowed to remove working SysV init support and refuse to add it back, and this is now what is happening here, so I thin…

Personally I find the /etc/init.d scripts to be crufty & in the way, & would rather not have them in my system. But I acknowledge there being other folks who for whatever reason prefer SysV style. And the maintainer's silent treatment is pretty harsh. I would like to give these other users a path forward, but at the same time, I don't want this file in /etc/init.d/ . It's in the way of a better functioning systemd sy…

Post by rektide » Thu, Sep 17, 2020, 2:57 AM UTC

grifferz wrote: post #43

rektide wrote: post #42

Earlier quoted context omitted.

Personally I find the /etc/init.d scripts to be crufty & in the way, & would rather not have them in my system. But I acknowledge there being other folks who for whatever reason prefer SysV style. And the maintainer's silent treatment is pretty harsh. I would like to give these other users a path forward, but at the same time, I don't want this file in /etc/init.d/ . It's in the way of a better functioning systemd sy…

Init scripts in /etc/init.d/ are not used when there is a systemd unit of the same name. Other than being in your filesystem they have zero effect on you.

Post by jjav » Fri, Sep 18, 2020, 7:30 AM UTC