> On Mon, 2005-10-17 at 14:36 -0600, Michael Loftis wrote:
>> Package: tar
>> Version: 1.14-2
>> Severity: important
>> 
>> ...
>> ./htdocs/nationwide/themes/templates/
>> ./htdocs/nationwide/themes/templates/old_files/
>> ./htdocs/nationwide/untitled/
>> tar: ./htdocs/class1/test/RoomSchedSymbols.fla: invalid sparse archive
>> member
>> tar: Skipping to next header
> 
> Is this still a problem with tar 1.15.1-2, currently in unstable?
> 

No, upgrading to 1.15.1-2 fixes it.

I hope the following makes it easy for you to reproduce

$ cat test.sh
#!/bin/bash

echo "........" > aoeu
dd if=/dev/zero of=sparse seek=10 count=1 bs=1M
echo "xxxxxxxx" > zaoeu

tar -cSf sparse.tar aoeu sparse zaoeu

tar -tvf sparse.tar aoeu
echo "Error level: $?"

tar -cf sparse.tar aoeu sparse zaoeu

tar -tvf sparse.tar aoeu
echo "Error level: $?"

---------

[EMAIL PROTECTED]:/tmp/tar-test$ sh test.sh
1+0 records in
1+0 records out
1048576 bytes transferred in 0,003606 seconds (290781099 bytes/sec)
-rw-r--r-- sunkan/sunkan     9 2005-10-19 11:15:29 aoeu
tar: sparse: invalid sparse archive member
tar: Skipping to next header
tar: Error exit delayed from previous errors
Error level: 2
-rw-r--r-- sunkan/sunkan     9 2005-10-19 11:15:29 aoeu
Error level: 0
[EMAIL PROTECTED]:/tmp/tar-test$ su
Password:
sunkan:/tmp/tar-test# aptitude
(Reading database ... 85530 files and directories currently installed.)
Preparing to replace tar 1.14-2 (using
.../archives/tar_1.15.1-2_i386.deb) ...
Unpacking replacement tar ...
Setting up tar (1.15.1-2) ...

Press return to continue.

sunkan:/tmp/tar-test# exit
[EMAIL PROTECTED]:/tmp/tar-test$ sh test.sh
1+0 records in
1+0 records out
1048576 bytes transferred in 0,003398 seconds (308596321 bytes/sec)
-rw-r--r-- sunkan/sunkan     9 2005-10-19 11:16:54 aoeu
Error level: 0
-rw-r--r-- sunkan/sunkan     9 2005-10-19 11:16:54 aoeu
Error level: 0
[EMAIL PROTECTED]:/tmp/tar-test$

/Andreas Sundstrom


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to