Your message dated Sun, 16 Dec 2018 07:41:53 +0000
with message-id <e1gyr3k-0007us...@eggs.gnu.org>
and subject line Re: rename --dryrun into --dry-run
has caused the Debian Bug report #580773,
regarding insserv: rename option --dryrun to the more commonly used --dry-run
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 ow...@bugs.debian.org
immediately.)
--
580773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: insserv
Version: 1.14.0-2
Severity: wishlist
Tags: patch
See also the man pages for:
patch, make, apt-get
for example.
You may consider doing something similar with the --showall option, i.e.
rename it to:
--show-all
The motivation is: 'dry' and 'run' (as well as 'show' and 'all') are two
distinctive words. Dictionaries reveal:
>From WordNet (r) 3.0 (2006) [wn]:
dry run
n 1: a practice session in preparation for a public performance
(as of a play or speech or concert); "he missed too many
rehearsals"; "a rehearsal will be held the day before the
wedding" [syn: {rehearsal}, {dry run}]
>From The Free On-line Dictionary of Computing (30 January 2010) [foldoc]:
dry run
<programming> To execute a program by hand, writing values of
variables and other run-time data on paper, in order to check
its operation and {control flow} or to track down a {bug} (as
part of {debugging}). A dry run is an extreme form of {desk
check} or {code review} and is practical only for fairly
simple programs, small amounts of data and simple external
interfaces. It was often performed {off-line} using a
{hardcopy} of the {source code}.
Dry runs were common practice in the days when access to
computers was limited but the availability of {screen editors}
and fast {compilers} makes {debugging by printf} a more
productive method in most cases. Sophisticated {debuggers}
that allow you to get the computer to step through your source
code line by line and show values of variables make even this
unnecessary.
(2006-11-27)
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages insserv depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
insserv recommends no packages.
Versions of packages insserv suggests:
ii bootchart 0.10~svn407-3.3 Boot process performance analyser
-- debconf information excluded
Cheers,
--
CristianDescription: renames the --dryrun to the more commonly used --dry-run.
From: Cristian Ionescu-Idbohrn <cristian.ionescu-idbo...@axis.com>
---
--- a/insserv.8.in
+++ b/insserv.8.in
@@ -267,7 +267,7 @@ LSB comment headers of scripts in the in
.BR \-p\ <path> ,\ \-\-path\ <path>
Specify path to init.d directory. Useful for testing.
.TP
-.BR \-n ,\ \-\-dryrun
+.BR \-n ,\ \-\-dry-run
Do not update symlinks.
.TP
.BR \-r ,\ \-\-remove
--- a/insserv.c
+++ b/insserv.c
@@ -2344,7 +2344,7 @@ static struct option long_options[] =
{
{"verbose", 0, (int*)0, 'v'},
{"config", 1, (int*)0, 'c'},
- {"dryrun", 0, (int*)0, 'n'},
+ {"dry-run", 0, (int*)0, 'n'},
{"default", 0, (int*)0, 'd'},
{"remove", 0, (int*)0, 'r'},
{"force", 0, (int*)0, 'f'},
@@ -2368,7 +2368,7 @@ static void help(const char *restrict co
printf(" -p <path>, --path <path> Path to replace " INITDIR ".\n");
printf(" -o <path>, --override <path> Path to replace " OVERRIDEDIR ".\n");
printf(" -c <config>, --config <config> Path to config file.\n");
- printf(" -n, --dryrun Do not change the system, only talk about it.\n");
+ printf(" -n, --dry-run Do not change the system, only talk about it.\n");
printf(" -s, --showall Output runlevel and sequence information.\n");
printf(" -d, --default Use default runlevels a defined in the scripts\n");
}
--- End Message ---
--- Begin Message ---
[2018-11-04 18:38] Benda Xu <hero...@gentoo.org>
> part text/plain 46
> tags 580773 -upstream +fixed-upstream
> thanks
Since insserv-1.18 is in sid, this bug is closed. I am sorry, that I
forgot to add apporiate (Closes: #nnn) entry into changelog.
--- End Message ---
