On Wed, Aug 21, 2013 at 11:08:14AM -0400, Joey Hess wrote:
> Chow Loong Jin wrote:
> > Attached.
>
> So, this is with the current unpatched pristine-tar:
>
> joey@gnu:~/tmp/x/foo>pristine-tar gendelta ~/foo.tar.gz ../delta
> joey@gnu:~/tmp/x/foo>pristine-tar gentar ../delta ../foo.tar.gz
> joey
Chow Loong Jin wrote:
> Attached.
So, this is with the current unpatched pristine-tar:
joey@gnu:~/tmp/x/foo>pristine-tar gendelta ~/foo.tar.gz ../delta
joey@gnu:~/tmp/x/foo>pristine-tar gentar ../delta ../foo.tar.gz
joey@gnu:~/tmp/x/foo>echo $?
0
Do you have a test case where the current one a
On Tue, Aug 20, 2013 at 01:27:44PM -0400, Joey Hess wrote:
> Chow Loong Jin wrote:
> > tar's -t and --files-from options implement quoting/unquoting of unprintable
> > characters, so we need to unquote the filenames before passing them to
> > mkpath.
>
> This patch does not seem complete.
> This
Chow Loong Jin wrote:
> tar's -t and --files-from options implement quoting/unquoting of unprintable
> characters, so we need to unquote the filenames before passing them to mkpath.
This patch does not seem complete.
This part of the code is not changed, and @manifest contains
filenames that have
Package: pristine-tar
Version: 1.26
Severity: normal
Tags: patch
Dear Maintainer,
When importing a tarball that has empty directories containing "\r" within their
path, pristine-tar re-creates these using '\r' (backslash r) rather than "\r"
(carriage return) in the filename, resulting in tar fail
5 matches
Mail list logo
