On Tue, Jan 09, 2001 at 06:16:54AM +0900, Junichi Uekawa wrote:
> To summarize what has been happening in debian-devel,
>
> The maintainer of tar has decided he wants to change the meaning of
Please be careful with your wording -- the upstream author has
made this change, not the debian maintain
> " " == safemode <[EMAIL PROTECTED]> writes:
> I have used tar with gzip and bzip2 in debian unstable and in
> each case users who use older versions of tar ( like 1.13.11 )
> were unable to decompress it.
Well, bzip2 is known. Just doesn't work anymore (see the big flameware
In Mon, 08 Jan 2001 15:21:30 -0500 safemode <[EMAIL PROTECTED]> cum veritate
scripsit :
> I have used tar with gzip and bzip2 in debian unstable and in each case
> users who use older versions of tar ( like 1.13.11 ) were unable to
> decompress it.
>
> [49: huff+mtf rt+rld]data integrity (CRC)
I have used tar with gzip and bzip2 in debian unstable and in each case
users who use older versions of tar ( like 1.13.11 ) were unable to
decompress it.
[49: huff+mtf rt+rld]data integrity (CRC) error in data
and such error messages like that . This troubles me greatly. Any info
about this?
4 matches
Mail list logo