Bug#944038: gpsd missing sysvinit script and breaks functionality on upgrade
On Sun, Nov 03, 2019 at 09:04:49PM +0100, Bernd Zeimetz wrote: > On 11/3/19 8:51 PM, Joerg Dorchain wrote: > > I would expect more > > explicit hints for such drastic changes from my favourite > > distribution. > > - Your favorite distribution uses systemd as default, expect init script > to be broken and/or not maintained at all. This is obvious. No problem with that. Hence this bug report to help maintaining. > I'm not maintaining something > I'm not going to use, not going to test, and that most people do not > care about. In my opinion a maintainer does not need to take personal responsability for everything. Offering as much flexibility and freedom to distro users, not imposing more rules than necessary is what I appreciate about Debian. "Works-for-me"-packages and having only one way is very limiting. Testing is what IMHO is done in the testing release. I tested and reported. I can also provide a patch, but I think it is trivial. Protection of minorities is IMHO also mentioned in the Debian social bylaws. Even if you reject bug reports for the lack of resources, allowing the use would be a good thing. For technical means, I explicitly point to the HANDS_OFF setting in /etc/mail/sendmail.conf in the sendmail package. > > - Your favorite distribution will soon have a GR about which init > system(s) will be supported in the future. If it forces me to maintain > init script, you can happily adopt the gpsd package. If not, you'll get > a very prominent hint. So I'm not going to change anything on the gpsd > package now. Sorry. My second point is is very unexpected change (withdrawal) of functionality. The packaging environment offers various ways to care for this. Bye, Joerg signature.asc Description: PGP signature
Bug#944038: gpsd missing sysvinit script and breaks functionality on upgrade
On 11/3/19 8:51 PM, Joerg Dorchain wrote: > I would expect more > explicit hints for such drastic changes from my favourite > distribution. - Your favorite distribution uses systemd as default, expect init script to be broken and/or not maintained at all. I'm not maintaining something I'm not going to use, not going to test, and that most people do not care about. - Your favorite distribution will soon have a GR about which init system(s) will be supported in the future. If it forces me to maintain init script, you can happily adopt the gpsd package. If not, you'll get a very prominent hint. So I'm not going to change anything on the gpsd package now. Sorry. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#944038: gpsd missing sysvinit script and breaks functionality on upgrade
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
Bug#944038: gpsd missing sysvinit script and breaks functionality on upgrade
Hi, > Justification: Breaks silently functionality on upgrade not if you'd use the default init system. > 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. > 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. Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#944038: gpsd missing sysvinit script and breaks functionality on upgrade
Package: gpsd Version: 3.19-2 Severity: Serious Justification: Breaks silently functionality on upgrade Hello, after upgrading to version 3.19-2, I saw two effects (admittingly after a while, but that makes it worse): - the gpsd was not running anymore - the init script is gone In my setup, gpsd is required to start at system boot with a sysv init. 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. Bye, Joerg signature.asc Description: PGP signature
