Bug#717595: Please check for update-rc.d "start" and "stop" argument usage

2019-11-01 Thread Paul Wise 
Control: tags -1 - moreinfo

Since this problem is still an issue with packages in the archive (like
x11-common), it would be nice to have lintian warn about the issues.

On Tue, 17 Dec 2013 10:10:58 +0100 Bastien ROUCARIES wrote:

> I am willing to implement this test but could you please provide a description

A reasonable description was already provided in the mail:

   The update-rc.d "start" and "stop" arguments are obsoleted and
   replaced by the "defaults" argument.  It is no longer possible to
   specify start and stop runlevel and sequence numbers; these must be
   provided by the LSB header of every init script.  If start and/or
   stop arguments are provided, these now act as if "defaults" had been
   used instead, and the extra runlevel and sequence information is
   discarded, and a warning will be issued.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#717595: Please check for update-rc.d start and stop argument usage

2013-12-17 Thread Bastien ROUCARIES 
control: tags -1 + moreinfo


It would be really great if lintian could check for and warn if the
a package calls update-rc.d in its maintainer scripts with start
or stop arguments.  Likewise for dh_installinit which passes
start and stop arguments to update-rc.d.

Regular expressions which could be used:

  update-rc.d.*[[:space:]]start[[:space:]]
  update-rc.d.*[[:space:]]stop[[:space:]]

  example packages: rsync, nfs-common

This doesn't handle quoting of start or stop in the scripts, but I've
not seen any in practice on my system.

And in debian/rules:

  dh_installinit.*--.*[[:space:]]start[[:space:]]
  dh_installinit.*--.*[[:space:]]start[[:space:]]

  example package: cron rpcbind

I can provide some explanatory text if needed.  Essentially, the
update-rc.d start and stop arguments are obsoleted and replaced by
the defaults argument.  It is no longer possible to specify start
and stop runlevel and sequence numbers; these must be provided by the
LSB header of every init script.  If start and/or stop arguments are
provided, these now act as if defaults had been used instead, and
the extra runlevel and sequence information is discarded, and a
warning will be issued.

I am willing to implement this test but could you please provide a description


-- 
To UNSUBSCRIBE, email to debian-lint-maint-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae2spay1_chxjrgc5ugv4ern39wib8jxlw_plho1o53tpu5...@mail.gmail.com