Debian Bug report logs - #688481
[copyright-format] Clarify that trailing slashes in directory names are invalid.

Package: debian-policy; Maintainer for debian-policy is Debian Policy List <debian-policy@lists.debian.org>; Source for debian-policy is src:debian-policy.

Reported by: Charles Plessy <plessy@debian.org>

Date: Sun, 23 Sep 2012 00:27:01 UTC

Severity: wishlist

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Policy List <debian-policy@lists.debian.org>:
Bug#688481; Package debian-policy. (Sun, 23 Sep 2012 00:27:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Charles Plessy <plessy@debian.org>:
New Bug report received and forwarded. Copy sent to Debian Policy List <debian-policy@lists.debian.org>. (Sun, 23 Sep 2012 00:27:04 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Charles Plessy <plessy@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: [copyright-format] Clarify that trailing slashes in directory names are invalid.
Date: Sun, 23 Sep 2012 09:23:25 +0900
Package: debian-policy
Severity: wishlist

Dear all,

as discussed on debian-devel@l.d.o, it may be useful to clarify that trailing
slashes in directory names in Files fields are invalid.  Only a few copyright
files were using trailing slashes at the beginning of this month.

(See http://lists.debian.org/20120905000419.GA1967@falafel.plessy.net)

The clarification could be the addition of a sentence in the paragraph
mentionning fnmatch(3), for instance the following.

  This syntax does not distinguish file names from directory names; trailing
  slashes after directory names are invalid.

In any case, I think that such a change can wait for the next revision of the
format.

Have a nice week-end,

-- 
Charles



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Policy List <debian-policy@lists.debian.org>:
Bug#688481; Package debian-policy. (Tue, 04 Feb 2014 18:21:09 GMT) Full text and rfc822 format available.

Acknowledgement sent to Nicolas Boulenguez <nicolas@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Policy List <debian-policy@lists.debian.org>. (Tue, 04 Feb 2014 18:21:09 GMT) Full text and rfc822 format available.

Message #10 received at 688481@bugs.debian.org (full text, mbox):

From: Nicolas Boulenguez <nicolas@debian.org>
To: Debian Bug Tracking System <688481@bugs.debian.org>
Subject: Re: [copyright-format] Clarify that trailing slashes in directory names are invalid.
Date: Tue, 4 Feb 2014 19:17:22 +0100
Package: debian-policy
Followup-For: Bug #688481

Please also make explicit that the space character cannot be escaped,
and how to select a path containing a space. Suggestion:

  This syntax does not distinguish file names from directory names; a
  trailing slash in a pattern will never match any actual path. A
  whole directory tree may be selected with a pattern like "foo/*".

  The space character, used to separate patterns, cannot be escaped
  with a backslash. A path like "foo bar" may be selected with a
  pattern like "foo?bar".



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Policy List <debian-policy@lists.debian.org>:
Bug#688481; Package debian-policy. (Sun, 09 Feb 2014 18:27:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>:
Extra info received and forwarded to list. Copy sent to Debian Policy List <debian-policy@lists.debian.org>. (Sun, 09 Feb 2014 18:27:04 GMT) Full text and rfc822 format available.

Message #15 received at 688481@bugs.debian.org (full text, mbox):

From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
To: Nicolas Boulenguez <nicolas@debian.org>, 688481@bugs.debian.org
Subject: Re: Bug#688481: [copyright-format] Clarify that trailing slashes in directory names are invalid.
Date: Sun, 9 Feb 2014 19:24:50 +0100
On Tue, Feb 04, 2014 at 07:17:22PM +0100, Nicolas Boulenguez wrote:
> Package: debian-policy
> Followup-For: Bug #688481
> 
> Please also make explicit that the space character cannot be escaped,
> and how to select a path containing a space. Suggestion:
> 
>   This syntax does not distinguish file names from directory names; a
>   trailing slash in a pattern will never match any actual path. A
>   whole directory tree may be selected with a pattern like "foo/*".
> 
>   The space character, used to separate patterns, cannot be escaped
>   with a backslash. A path like "foo bar" may be selected with a
>   pattern like "foo?bar".

This looks like a rather ugly solution ? Proper quoting support might
be in order.

Cheers,
Bill.



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Policy List <debian-policy@lists.debian.org>:
Bug#688481; Package debian-policy. (Sun, 09 Feb 2014 19:03:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Nicolas Boulenguez <nicolas.boulenguez@free.fr>:
Extra info received and forwarded to list. Copy sent to Debian Policy List <debian-policy@lists.debian.org>. (Sun, 09 Feb 2014 19:03:05 GMT) Full text and rfc822 format available.

Message #20 received at 688481@bugs.debian.org (full text, mbox):

From: Nicolas Boulenguez <nicolas.boulenguez@free.fr>
To: 688481@bugs.debian.org
Subject: Re: Bug#688481: [copyright-format] Clarify that trailing slashes in directory names are invalid.
Date: Sun, 9 Feb 2014 20:01:49 +0100
On Sun, Feb 09, 2014 at 07:24:50PM +0100, Bill Allombert wrote:
> On Tue, Feb 04, 2014 at 07:17:22PM +0100, Nicolas Boulenguez wrote:

> >   The space character, used to separate patterns, cannot be escaped
> >   with a backslash. A path like "foo bar" may be selected with a
> >   pattern like "foo?bar".
> 
> This looks like a rather ugly solution ? Proper quoting support might
> be in order.

I doubt that increasing the complexity of this format is worth the
while. Only paths in a fixed known tarball have to be checked.

If a same upstream tarball ever happens to contain two paths only
differing by spaces characters, but with distinct licenses or
Files-Excluded status (can you imagine a sane example?), then
exclusion by a later stanza will provide a work-around:

Files: "foo?bar"
# selects "foo bar" but not "foo_bar" because next stanza takes
# precedence.

Files: "foo_bar"



Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Fri Apr 18 06:01:31 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.