Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2017-08-04 Thread Sean Whitton
Hello Mike, On Thu, Aug 03, 2017 at 03:09:30PM +, Mike Gabriel wrote: > How would differentiate between a blank in a file name and a blank as a > separator? If you needed blanks in filenames, you'd use a line-based list. -- Sean Whitton signature.asc Description: PGP signature

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2017-08-03 Thread Mike Gabriel
HI Sean, On Do 03 Aug 2017 17:06:19 CEST, Sean Whitton wrote: Hello Russ, On Wed, Aug 02, 2017 at 11:54:52AM -0700, Russ Allbery wrote: I like solution (a), honestly. I think we could just add backslash as an escape character that escapes anything other than a newline and have the problem

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2017-08-03 Thread Sean Whitton
Hello Russ, On Wed, Aug 02, 2017 at 11:54:52AM -0700, Russ Allbery wrote: > I like solution (a), honestly. I think we could just add backslash as an > escape character that escapes anything other than a newline and have the > problem basically go away. It would require a new version of the

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2017-08-02 Thread Russ Allbery
Sean Whitton writes: > On Sat, Jan 02, 2016 at 10:49:04AM +, Mike Gabriel wrote: >> At the moment, we are not able to exactly specify file paths of >> files/folders containing blanks in debian/copyright when complying with >> the DEP-5 specs. (I agree that it is

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2017-08-02 Thread Sean Whitton
On Sat, Jan 02, 2016 at 10:49:04AM +, Mike Gabriel wrote: > At the moment, we are not able to exactly specify file paths of > files/folders containing blanks in debian/copyright when complying with the > DEP-5 specs. (I agree that it is indeed uncommon as a developer to use > blanks in

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2016-01-02 Thread Mike Gabriel
Control: retitle -1 DEP-5 does not support filenames with blanks Control: reassign -1 debian-policy Hi all, On Sa 02 Jan 2016 10:16:26 CET, Niels Thykier wrote: On Sat, 02 Jan 2016 09:05:31 + Mike Gabriel wrote: Package: lintian Version: 2.5.39 When

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2016-01-02 Thread Mike Gabriel
Package: lintian Version: 2.5.39 When checking the build of onboard 1.1.2-2, I get this from lintian: """ I: onboard source: wildcard-matches-nothing-in-dep5-copyright layouts/Full (paragraph at line 156) N: N:The wildcard that was specified matches no file in the source tree. This N:

Bug#809637: debian/copyright checks fail on upstream filenames containing blanks

2016-01-02 Thread Niels Thykier
On Sat, 02 Jan 2016 09:05:31 + Mike Gabriel wrote: > Package: lintian > Version: 2.5.39 > > When checking the build of onboard 1.1.2-2, I get this from lintian: > > """ > [...] > """ > > Reason: upstream tarball contains files with spaces. > > Greets, >