Bug#949690: debian-policy: "service unit should have the same name as the package" seems too strong

2020-01-23 Thread Bill Allombert
On Thu, Jan 23, 2020 at 12:43:34PM -0800, Russ Allbery wrote: > Simon McVittie writes: > > > If a package has a single system service with a systemd service unit, > > and the system service's name does not match the package's name, current > > Policy implies that this is probably a (non-RC) bug.

Bug#949690: debian-policy: "service unit should have the same name as the package" seems too strong

2020-01-23 Thread Russ Allbery
Simon McVittie writes: > If a package has a single system service with a systemd service unit, > and the system service's name does not match the package's name, current > Policy implies that this is probably a (non-RC) bug. > I think that's too strong. In particular, because the name of the ser

Bug#949690: debian-policy: "service unit should have the same name as the package" seems too strong

2020-01-23 Thread Michael Biebl
[..] Thanks for bringing that up, Simon. I share your concern and agree with your conclusion. As an example, I explicitly decided to keep the name NetworkManager.service in the network-manager package. I did create an alias/symlink network-manager.service and ship that in the package, to shadow/m

Bug#949690: debian-policy: "service unit should have the same name as the package" seems too strong

2020-01-23 Thread Simon McVittie
Package: debian-policy Version: 4.5.0.0 Severity: minor X-Debbugs-Cc: syst...@packages.debian.org If a package has a single system service with a systemd service unit, and the system service's name does not match the package's name, current Policy implies that this is probably a (non-RC) bug. I t