[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#485705: lintian: doesn't properly detect comma in control file email address quoted strings



On Tue, 2008-06-10 at 21:57 -0700, Russ Allbery wrote:
> Adam C Powell IV <hazelsct@debian.org> writes:
> 
> > Package: lintian
> > Version: 1.24.0
> > Severity: minor
> >
> > Greetings,
> >
> > An email address in a control field, e.g. Uploaders, should work with a
> > comma in a quoted string, such as of the form:
> >   "Smith, John" <john.smith@gmail.com>
> > See for example RFC822 Appendix A.1.3.
> 
> Policy doesn't specify that Uploaders is an RFC 2822 From header.  It's
> not an unreasonable desire that it be so specified, but so far as I know,
> nothing in Debian that parses those fields implements a full RFC 2822 From
> parser, and Uploaders containing commas breaks other software as well.
> 
> I think this requires a Policy change before Lintian knows which way to
> jump.  If this is supposed to be an RFC 2822 From header, Policy should
> say so.  Currently, Policy says:
> 
>     List of the names and email addresses of co-maintainers of the
>     package, if any. If the package has other maintainers beside the one
>     named in the Maintainer field, their names and email addresses should
>     be listed here. The format is the same as that of the Maintainer tag,
>     and multiple entries should be comma separated.
> 
> which if anything says that the current behavior of Lintian and other
> tools is correct, as there's nothing there about it being possible to
> escape commas.

Please read again.  5.6.3, which you quoted, refers to the Maintainer
tag specified in 5.6.2, which in turn specifies RFC822 format, which
permits quoted strings, including commas.  The long lintian error
message also mentions 5.6.2 (probably in error).  Or am I reading this
wrong?

> This problem is new with Uploaders; since Maintainer doesn't take a list,
> it was never ambiguous.  Commas in names have never worked for Uploaders
> since the introduction of the feature so far as I know.

I see.  Does this mean that lintian is consistent with the uploading
framework, and I will have trouble uploading?

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

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


Reply to: