Package: bzip2
Version: 1.0.3-2
Severity: minor
When trying to bzip2 -d an empty file, I get very confusing errors:
$ touch empty.bz2
$ bzip2 -d empty.bz2
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: No such file or directory
Input file = empty.bz2, output file = empty
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Deleting output file empty, if it exists.
$ cat /dev/null | bzip2 -d
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Invalid argument
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
$
Now I understand that empty files aren't supposed to be bunzip2'ed, but
a simple "bzip2: Input file contains do data" or the like would be much
more understandable than the confusing and even misleading errors above
(those 'possible reasons' are plain nonsense).
Using kernel 2.6.15.6, libbz2-1.0 1.03-2 and libc6 2.3.6-7
For those of you who wonder who in their right mind would try to bunzip2
an empty file (which was obviously not created by bzip2 in the first
place): apt-get does (see bug #316337), which produces an error message
identical to the second one in my transcript above.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
