Your message dated Thu, 06 Sep 2018 20:04:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#717592: dh_installinit: Please do not pass through
start and stop parameters to update-rc.d
has caused the Debian Bug report #717592,
regarding dh_installinit: Please do not pass through start and stop parameters
to update-rc.d
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
717592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717592
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debhelper
Version: 9.20130630
Severity: normal
Hi Joey,
As you're undoubtedly aware, we've been using LSB headers in place of
static sequence numbers for a good couple of releases now. With
wheezy, we migrated completely away from static ordering to dynamic
ordering. This means that the "start nn n n" and "stop nn n n"
parameters are now essentially pointless--update-rc.d has long
ignored them when dependency-based boot was in use. For wheezy in
practice it will always ignore them since dependency-based boot is
required. In jessie we removed start and stop entirely; they still
exist internally, but are just aliases for "defaults", and issue a
warning if used; all runlevel information is obtained from the LSB
headers.
It would be great if dh_installinit could stop calling update-rc.d
with start or stop arguments, but initially just warning if the
params contains "start" or "stop" arguments would be a good first
step. I'm not sure of whether it's practical or not to just pass
"defaults" if "start" or "stop" are detected--I imagine there might
be complications, so just warning might be better?
I'll also look at getting lintian warnings added which should be
able to pick up dh_installinit and update-rc.d usage and also warn.
Regards,
Roger
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (550, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages debhelper depends on:
ii binutils 2.23.52.20130620-1
ii dpkg 1.16.10
ii dpkg-dev 1.16.10
ii file 1:5.14-2
ii man-db 2.6.5-2
ii perl 5.14.2-21
ii po-debconf 1.0.16+nmu2
debhelper recommends no packages.
Versions of packages debhelper suggests:
ii dh-make 0.62
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 20 Aug 2013 13:13:42 -0400 Joey Hess <[email protected]> wrote:
> Roger Leigh wrote:
> > ignored them when dependency-based boot was in use. For wheezy in
> > practice it will always ignore them since dependency-based boot is
> > required. In jessie we removed start and stop entirely; they still
> > exist internally, but are just aliases for "defaults", and issue a
> > warning if used; all runlevel information is obtained from the LSB
> > headers.
> >
> > It would be great if dh_installinit could stop calling update-rc.d
> > with start or stop arguments, but initially just warning if the
> > params contains "start" or "stop" arguments would be a good first
> > step. I'm not sure of whether it's practical or not to just pass
> > "defaults" if "start" or "stop" are detected--I imagine there might
> > be complications, so just warning might be better?
>
> I am uncomfortable with debhelper commands parsing parameters passed
> after -- and producing warnings for two reasons:
>
> 1. It's an abstraction violation for it to look at those parameters.
> 2. Debhelper's job is not to produce lots of verbose warnings about
> things possibly wrong with the package it's building.
>
> If update-rc.d no longer has any options which it makes sense to be
> propigated from dh_installinit then it could stop sending the -- options
> to it at all. I'm not sure if the disable|enable option could make sense
> to be used.
>
> > I'll also look at getting lintian warnings added which should be
> > able to pick up dh_installinit and update-rc.d usage and also warn.
>
> That seems much more appropriate.
>
> --
> see shy jo
Closing an old wontfix bug.
Thanks,
~Niels
--- End Message ---
