found 374310 1.14.2-2 close 374310 1.15.91-1 thanks Hi!
I tried to reproduce this bug using tar 1.15.91-1 from sid and 1.14.2-2 from sarge: I created a 6GB sparse file containing 1GB of real (urandom) data, which I compressed with tar cS (no gzip/bzip, as that seems irrellevant for this bug) with both the sid and sarge version of tar. I then untarred both the sparse file with both versions of tar, resulting in 4 files, of which I compared the sizes and md5sums with the original file. The results: -rw------- 1 bas bas 5.9G 2006-06-24 17:45 sparsefile_original -rw------- 1 bas bas 1.9G 2006-06-24 17:45 sparsefile_sarge_sarge -rw------- 1 bas bas 1.9G 2006-06-24 17:45 sparsefile_sarge_sid -rw------- 1 bas bas 5.9G 2006-06-24 17:45 sparsefile_sid_sarge -rw------- 1 bas bas 5.9G 2006-06-24 17:45 sparsefile_sid_sid 53b5a6811bb6a6080ca394d30f7f08ca sparsefile_original aec01d4498d01b777df87cf52a5beb73 sparsefile_sarge_sarge aec01d4498d01b777df87cf52a5beb73 sparsefile_sarge_sid 53b5a6811bb6a6080ca394d30f7f08ca sparsefile_sid_sarge 53b5a6811bb6a6080ca394d30f7f08ca sparsefile_sid_sid (sparsefile_sarge_sid was tarred with tar from sarge and untarred with tar from sid, etc) I can thus confirm that the files that were tarred using the sarge version of tar, unpacked to a corrupt file with a wrong size, regarless of the tar version used to untar the archive. I am tagging this bug accordingly. -- Kind regards, +--------------------------------------------------------------------+ | Bas Zoetekouw | GPG key: 0644fab7 | |----------------------------| Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | +--------------------------------------------------------------------+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
