Your message dated Wed, 22 May 2013 00:47:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#219402: templates poorly punctuated
has caused the Debian Bug report #219402,
regarding templates poorly punctuated
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.)


-- 
219402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219402
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ssh
Version: 1:3.6.1p2-9

Several of the entries in ssh's debconf templates files are asking
questions, but their descriptions don't end with an '?' mark.  If
debconf is configured to use the readline frontend, or perhaps others
with few visual cues as to what's going on, this punctuation is quite
important.




--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:4.3p2-1

On Thu, Nov 06, 2003 at 10:00:58AM +0000, Phil Blundell wrote:
> Several of the entries in ssh's debconf templates files are asking
> questions, but their descriptions don't end with an '?' mark.  If
> debconf is configured to use the readline frontend, or perhaps others
> with few visual cues as to what's going on, this punctuation is quite
> important.

I appear to have fixed this a long time ago:

openssh (1:4.3p2-1) unstable; urgency=low

  [...]
  * Rephrase ssh/new_config and ssh/encrypted_host_key_but_no_keygen debconf
    templates to make boolean short descriptions end with a question mark
    and to avoid use of the first person.
  [...]

 -- Colin Watson <[email protected]>  Fri, 12 May 2006 12:48:24 +0100

Thanks,

-- 
Colin Watson                                       [[email protected]]

--- End Message ---

Reply via email to