On Sun, Nov 03, 2019 at 04:39:59PM +0100, Bernd Zeimetz wrote: > > Justification: Breaks silently functionality on upgrade > > not if you'd use the default init system.
Policy says all init system are equally supported. > > > In my setup, gpsd is required to start at system boot with a sysv > > init. > > That is not supported by the gpsd upstream anymore, all the > hotplugging/udev rules require systemd (which makes a lot of sense!), > and to avoid a mess in debugging this, I'm not going to change this. Hm. Upstream has an init script... If you do not accept bug reports about sysvinit, make this clear in a README.Debian, but please still ship the script, even if it is under documenation. Other packages, e.g. sendmail, have an explicit config setting where the admin has all freedom with own config at the price of explicitly getting no maintainer support. > > > > The upgrading process stops the running gpsd, and without the > > init script, it is not restarted, resulting in a system without > > gps information. > > > > Please bring the init script back. > no. please use systemd. systemd is not an option. If you have reasons not supporting sysvinit (if it is lack of time, I could help), then at least do not siliently have a disrupting break in functionality. The package system has ways to tell the admin that he needs to do something, like e.g. an acknowledgement on upgrade, or at least a NEWS.Debian file. Just without a decent warning stopping gpsd and not telling about it is IMHO at the very least impolite. I would expect more explicit hints for such drastic changes from my favourite distribution. Thanks for considering. Bye, Joerg
signature.asc
Description: PGP signature
