Bug#254998: marked as done (Please follow policy 9.4 in printing "working" messages with ellipses ("..."))
Your message dated Fri, 04 Feb 2005 18:05:06 -0600
with message-id <87u0orkh1p.fsf@glaurung.internal.golden-gryphon.com>
and subject line This is not a policy bug.
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Jun 2004 08:26:02 +0000
>From jdthood@yahoo.co.uk Fri Jun 18 01:26:02 2004
Return-path: <jdthood@yahoo.co.uk>
Received: from post-20.mail.nl.demon.net [194.159.73.1]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BbEhG-00033y-00; Fri, 18 Jun 2004 01:26:02 -0700
Received: from [82.161.38.140] (helo=localhost)
by post-20.mail.nl.demon.net with esmtp (Exim 3.36 #2)
id 1BbEhB-000Gcq-00; Fri, 18 Jun 2004 08:25:57 +0000
Received: by localhost (Postfix, from userid 1001)
id 817A312D0F9; Fri, 18 Jun 2004 10:24:05 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Thomas Hood <jdthood@yahoo.co.uk>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Please follow policy 9.4 in printing "working" messages with ellipses ("...")
X-Mailer: reportbug 2.61
Date: Fri, 18 Jun 2004 10:24:05 +0200
Message-Id: <20040618082405.817A312D0F9@localhost>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: dpkg
Version: 1.10.22
Severity: minor
While it is working dpkg prints messages like these:
Setting up foo (1.0) ...
Policy 9.4 gives the following advice for the writing of initscripts.
If you want to express that the computer is working on
something (that is, performing a specific task, not starting
or stopping a program), we use an "ellipsis" (three dots:
"..."). Note that we don't insert spaces before or after the
dots. If the task has been completed we write "done." and a
line feed.
Thus initscripts print messages like these:
Initialising bar...done.
When packages are being installed initscripts sometimes get run;
thus one sees a mixture of dpkg-style "working" messages and
initscripts-style "working" messages. Consistency of style would
be better aesthetically so I suggest that dpkg's messages be
changed to follow the policy for initscripts' messages.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (900, 'unstable'), (700, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=en_IE@euro, LC_CTYPE=en_IE@euro
Versions of packages dpkg depends on:
ii dselect 1.10.22 a user tool to manage Debian packa
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
-- no debconf information
---------------------------------------
Received: (at 254998-done) by bugs.debian.org; 5 Feb 2005 00:08:34 +0000
>From srivasta@debian.org Fri Feb 04 16:08:34 2005
Return-path: <srivasta@debian.org>
Received: from host-12-107-230-171.dtccom.net (glaurung.internal.golden-gryphon.com) [12.107.230.171]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CxDV3-00035r-00; Fri, 04 Feb 2005 16:08:34 -0800
Received: from glaurung.internal.golden-gryphon.com (localhost [127.0.0.1])
by glaurung.internal.golden-gryphon.com (8.13.3/8.13.3/Debian-4) with ESMTP id j1505Auc014434
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
for <254998-done@bugs.debian.org>; Fri, 4 Feb 2005 18:05:10 -0600
Received: (from srivasta@localhost)
by glaurung.internal.golden-gryphon.com (8.13.3/8.13.3/Submit) id j15056ra014366;
Fri, 4 Feb 2005 18:05:06 -0600
X-Authentication-Warning: glaurung.internal.golden-gryphon.com: srivasta set sender to srivasta(va, manoj)@debian.org using -f
From: Manoj Srivastava <srivasta@debian.org (va, manoj)>
To: 254998-done@bugs.debian.org
Subject: This is not a policy bug.
Organization: The Debian Project
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)
(i686-pc-linux-gnu)
X-URL: http://www.debian.org/%7Esrivasta/
Mail-Copies-To: nobody
X-Face: #q.#]5@vq!Jz+E0t_/;Y^gTjR\T^"B'fbeuVGiyKrvbfKJl!^e|e:iu(kJ6c|QYB57LP*|t
&YlP~HF/=h:GA6o6W@I#deQL-%#.6]!z:6Cj0kd#4]>*D,|0djf'CVlXkI,>aV4\}?d_KEqsN{Nnt7
78"OsbQ["56/!nisvyB/uA5Q.{)gm6?q.j71ww.>b9b]-sG8zNt%KkIa>xWg&1VcjZk[hBQ>]j~`Wq
Xl,y1a!(>6`UM{~'X[Y_,Bv+}=L\SS*mA8=s;!=O`ja|@PEzb&i0}Qp,`Z\:6:OmRi*
X-Hashcash: 1:25:050205:254998-done@bugs.debian.org::xUmIaCA2VHe8rajp:0000000000000000000000000000000000GK1Z
Date: Fri, 04 Feb 2005 18:05:06 -0600
Message-ID: <87u0orkh1p.fsf@glaurung.internal.golden-gryphon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-CRM114-Score: -76.5579
X-CRM114-Status: Good ( pR: -76.5579 )
X-Spam-Value: -18.5966611111111
X-SA-Rep: -18.5966611111111 ALL_TRUSTED,BAYES_00,HASHCASH_25
X-Scanned-By: MIMEDefang version 2.48 (www . roaringpenguin . com / mimedefang) on 127.0.0.1
Delivered-To: 254998-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Hi,
The fact that dpkg does not follow what the policy recommends
is by no means a policy bug. It also is not clear that section 9.4
applies to dpkg in the first place (dpkg is not an initscript). I
understand the aesthetic motivation, but thefact that packages are
sometimnes restarted during upgrades/installs and the dpkg output
does not jell with initscript output does not imply that initscript
output policy is somehow buggy. If you really think this is a bug,
propose an alternative, along with a transition plan.
manoj
--
"Silent gratitude isn't very much use to anyone." Stearn
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: