Bug#989155: dh_installinit: when upgrading to a version that adds --no-restart-after-upgrade, the service is not restarted

2021-11-01 Thread Michael Biebl
On 29.10.21 19:39, Ryan Tandy wrote: Hi Michael, On Fri, Oct 29, 2021 at 09:51:46AM +0200, Michael Biebl wrote: If you use "--no-restart-after-upgrade", why do you expect the service to be restarted? The man page describes --no-restart-after-upgrade:  Undo a previous

Bug#989155: dh_installinit: when upgrading to a version that adds --no-restart-after-upgrade, the service is not restarted

2021-10-29 Thread Ryan Tandy
Hi Michael, On Fri, Oct 29, 2021 at 09:51:46AM +0200, Michael Biebl wrote: If you use "--no-restart-after-upgrade", why do you expect the service to be restarted? The man page describes --no-restart-after-upgrade: Undo a previous --restart-after-upgrade (or the default of compat 10). If

Bug#989155: dh_installinit: when upgrading to a version that adds --no-restart-after-upgrade, the service is not restarted

2021-10-29 Thread Michael Biebl
On Wed, 26 May 2021 20:44:24 -0700 Ryan Tandy wrote: Package: debhelper Version: 13.3.4 Severity: normal Control: affects -1 slapd Dear maintainer, It looks like if I currently use dh_installinit --restart-after-upgrade (the default), and in a newer version I change it to use

Bug#989155: dh_installinit: when upgrading to a version that adds --no-restart-after-upgrade, the service is not restarted

2021-05-26 Thread Ryan Tandy
Package: debhelper Version: 13.3.4 Severity: normal Control: affects -1 slapd Dear maintainer, It looks like if I currently use dh_installinit --restart-after-upgrade (the default), and in a newer version I change it to use --no-restart-after-upgrade, then when I upgrade to that newer