Your message dated Mon, 11 May 2015 13:28:30 +0500
with message-id <20150511082830.ga2...@belkar.wrar.name>
and subject line Closing
has caused the Debian Bug report #160827,
regarding Standardize syntax of the name in the Maintainer control field
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.)


-- 
160827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=160827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 3.7.2.2
Severity: wishlist

Hello,

 enrico> Just when I wanted to split Maintainer fields my commas, I
         stumble on Maintainer: Adam C. Powell, IV <hazel...@debian.org>
 enrico> Now I'll just split Uploader: gfields by commas
    liw> enrico, hmm, should the Maintainer field not be an rfc822
         compatible e-mail address spec?
 enrico> liw: I'll check the policy
    liw> hmm, the policy only mentions a problem with periods
 enrico> liw: and only the mail address seems to be RFC822

Section 5.6.2. `Maintainer' says:

     The package maintainer's name and email address.  The name should come
     first, then the email address inside angle brackets `<>' (in RFC822
     format).

     If the maintainer's name contains a full stop then the whole field
     will not work directly as an email address due to a misfeature in the
     syntax specified in RFC822; a program using this field as an address
     must check for this and correct the problem if necessary (for example
     by putting the name in round brackets and moving it to the end, and
     bringing the email address forward).

Now, the field "Adam C. Powell, IV <hazel...@debian.org>" seems to be
legal according to current policy.  However, later in "5.6.3.
`Uploaders'" the policy says:

     The format is the same as that of the Maintainer tag, and multiple
     entries should be comma separated.

This would imply that commas should not be used in the Maintainer field.

This is not a big problem for me now, since I can work around the issue
by using two different functions to handle Maintainer and Uploaders, one
that does not try to split on commas and the other that does.

However, this issue seems to require a little clarification.


Ciao,

Enrico


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)

-- no debconf information


--- End Message ---
--- Begin Message ---
The current Policy (since 3.8.1.0) says "All control files must be encoded
in UTF-8." and the current practice is to use UTF-8 in Maintainer: field
values.

-- 
WBR, wRAR

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to