Re: tar enhancements in 't' & 'x' (was Corrupted tar-ball in Cygwin-x86_64)

[Linda Walsh <cygwin@tlinx.org>]

Angelo Graziosi wrote:
> Il 18/01/2014 13.01, Angelo Graziosi ha scritto:
>> When I try to update my Cygwin64 installation (on a virtualBox Win7-64
>> installation) I get an error about the cygwin32-1.7.27-1.tar.xz package
>> which seems corrupted.
>>
>> This is confirmed from command line on which i get:
>>
>> $ tar -rf cygwin32-1.7.27-1.tar.xz
> 
> There is a typo here (on my part) which seems to have generated some 
> confusion... :(
> 
> The command I have run to confirm the corrupted tar file was
> 
> $ tar -tf cygwin32-1.7.27-1.tar.xz
----
I thought it was the case that 'a' was required on t/x as well as
'c', but can only verify that it used to need some extension it
could recognize, but now it figures it out w/no extension.

I.e.:
(old):
Astarte:/tmp> tar caf xxx.tar.xz 
server-0815527C63B5A57106C26703B2473B023EC30A19.xkm
Astarte:/tmp> mv xxx.tar.xz xxx
Astarte:/tmp> tar tf xxx
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
(new)
/tmp> tar caf xx.tar.xz xx.sh
/tmp> mv xx.tar.xz xx
/tmp> tar tf xx
xx.sh
----

Guess somewhere I assumed 'a' was required for automatic compression
recognition... but only on 'c' it seems...

It is the case tar will decode even files w/o extensions...neat!.



> Anyway, the most important thing is that now Yaakov has fixed the 
> corrupted tar-ball (http://cygwin.com/ml/cygwin/2014-01/msg00249.html)
---
Well that's the important part!



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple