Back in January of 2005, Joey Hess pointed out in a bug report against
Debian's package of tar that's actually an enhancement request, and as I
clean up my open bug list in preparation for the next Debian release I
realized we never passed it along.
The concern expressed is that tar is vulnerable
A Debian user pointed out a while back that the tar man page doesn't
mention that verbosity can be increased by using multiple -v or
--verbose options, nor does it mention the maximum verbosity level.
More details in the bug log at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602898
Regar
A while back, a Debian developer observed that using --delete can in
at least some cases cause filenames after the deleted ones to be
corrupted. There's a test case in the bug log at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869087
I was able to confirm that this still happens with t
Many years ago a Debian user pointed out that the tar info page has
conflicting definitions for the -o option. I just confirmed that this
is still true in 1.30. Please accept my apologies for letting this rot
in our bug tracking system for so long before passing it along. More
details in the bug
Some years ago, a Debian user pointed out that tar behaves badly when
given legal (but weird?) POSIX filenames like
\fhd =
or as of a follow-up from another user against version 1.29, even
Студия_07\04\12.meta1-conv
More details in the Debian bug log at
https://bugs.debian.org/cg
A Debian user of tar pointed out a while back that --warning=none
doesn't always work as expected. The example involved using options
'df' to compare a simple tar file to a directory tree with a removed
file. I used the procedure in the bug log to confirm this still happens
with tar 1.30:
http
A Debian user of tar points out that the man page documents --preserve,
but tar doesn't actually support it, complaining that --preserve is
ambiguous. Full details in the Debian bug log at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847993
Regards,
Bdale
signature.asc
Description: PGP
Bdale Garbee ha escrit:
> A Debian user pointed out a while back that the tar man page doesn't
> mention that verbosity can be increased by using multiple -v or
> --verbose options, nor does it mention the maximum verbosity level.
Thanks. I fixed this.
Regards,
Sergey
Hi Bdale,
> Many years ago a Debian user pointed out that the tar info page has
> conflicting definitions for the -o option.
Thanks. Fixed this in 97d89515 as well.
Regards,
Sergey
> Back in January of 2005, Joey Hess pointed out in a bug report against
> Debian's package of tar that's actually an enhancement request, and as I
Thanks. However, this report is based on a premise that doesn't seem
valid to me:
"Anything with a colon will do, though a real rmt volume
probab
Hi Bdalem
> A Debian user of tar points out that the man page documents --preserve,
> but tar doesn't actually support it, complaining that --preserve is
> ambiguous.
Removed obsolete description (97d89515).
Regards,
Sergey
Bdale Garbee ha escrit:
> Some years ago, a Debian user pointed out that tar behaves badly when
> given legal (but weird?) POSIX filenames like
>
> \fhd =
"For instance, the command
tar vzcf file.tar.gz '\fhd ='
exits with the following error:
tar: \fhd =: Cannot s
Bdale Garbee ha escrit:
> A Debian user of tar pointed out a while back that --warning=none
> doesn't always work as expected. The example involved using options
> 'df'
The purpose of the -d option is to report differences between the file
system and the contents of the archive. And this messag
Sergey Poznyakoff writes:
> This is the correct behavior. The --unquote option is used by default,
Ah! Right, thanks for the reply. I'll close this bug with an
explanation based on this email.
Bdale
signature.asc
Description: PGP signature
14 matches
Mail list logo
