Bug#733111: update uscan Files-Excluded parsing to support escaped names

[Csillag Tamas]

Hi,

On Wed, Dec 25, 2013 at 09:49:45AM -0800, Russ Allbery wrote:
...
> In order to support file names that contain whitespace, uscan's parsing
> of Files-Excluded needs to handle the character escaping protocol.  The
> following code should correctly handle foo\ bar, as well as the other
> more pathological cases such as foo\\ bar (which is two files).

Following up on the regexp and the bugreport created by Russ:

I created a patch and tested it with a Files-excluded statement in
d/copyright.
I found an issue that it does not split on newlines.
Russ: If you can update the regexp to cover these use case the better.
(and thanks for the current one, my Perl knowledge is lacking when it comes to
regexpes like this one :)
In the meanwhile I updated the script to replace newlines with
whitespaces to get the same result.

I include a patch.

A separate issue is that when in dehs mode uscan should return after
repacking the archive with files removed the new filename.
I include a separate patch for this one.

I have all of these in my git repo available for conveniance:
git://cstamas.hu/git/devscripts.git

Regards,
 Tamas
-- 
CSILLAG Tamas (cstamas) - http://cstamas.hu/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: uscan-dehs-fix.patch
Type: text/x-diff
Size: 704 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20131226/5faa5510/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uscan-spaces-in-filenames.patch
Type: text/x-diff
Size: 1034 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20131226/5faa5510/attachment-0001.patch>