problem resolved (was: Re: amavisd-new chokes on all tar files?)

[John Clements]

On May 30, 2011, at 2:38 PM, John Clements wrote:
>>> So: is this a known bug? Is it a bug in amavisd, or in pax?
>>> 
>>> I'm using debian, where this version of amavisd-new has version
>>> "1:2.6.4-3". My machine's version of "pax" is 1:20090728-1.
>> 
>> Looks to me like a bug in your pax.
>> 
>> Try listing the contents of your tar sample file from a command line.
>> On my host it gives:
>> 
>> $ pax -v <foo.tar 
>> -rw-r--r--  1 501              wheel         92 May 25 19:09 foo
>> pax: ustar vol 1, 1 files, 2048 bytes read, 0 bytes written.
>> 
>> $ cpio -i -t -v <foo.tar 
>> -rw-r--r--   0 clements wheel          92 May 25 19:09 foo
>> 4 blocks
>> 
>> $ tar tvf foo.tar 
>> -rw-r--r--  0 clements wheel      92 May 25 19:09 foo
> 
> On my machine:
> 
> clements at computer:/tmp$ pax -v < /tmp/foo.tar
> -rw-r--r--  1 clements root     4294967354 May 30 14:32 foo
> pax: ustar vol 1, 1 files, 2048 bytes read, 13804660788098922804 bytes written.
> clements at computer:/tmp$ ls
> backuppc   f        id_rsa.pub    mail.rr.com.log  orbit-clements
> config.pl  foo.tar  localhost.pl  main.cf
> clements at computer:/tmp$ cpio -i -t -v < foo.tar
> cpio: Malformed number 000644 
> cpio: Malformed number 000000 
> cpio: Malformed number 00000000072 
> cpio: Malformed number 11571006333 
> cpio: Malformed number 000000 
> cpio: Malformed number 000000 
> -r-Sr-S---   1 clements root          464 Jan 29  2029 foo
> 3 blocks
> clements at computer:/tmp$ tar tvf foo.tar
> -rw-r--r-- clements/wheel   58 2011-05-30 14:32 foo
> clements at computer:/tmp$ 
> 
> So... definitely a problem with pax :).

Just to close this thread; upgrading from version 1:20090728-1 to version 1:20090728-2 (using the debian labeling scheme) of pax has successfully resolved this problem.

Cheers!

John Clements