Bug#374310: tar: wrong size of 6GB sparse file after extraction

2006-06-26 Thread Bdale Garbee
On Sat, 2006-06-24 at 18:19 +0200, Bas Zoetekouw wrote: > 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. Thanks for y

Processed: Re: Bug#374310: tar: wrong size of 6GB sparse file after extraction

2006-06-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > found 374310 1.14.2-2 Bug#374310: tar: wrong size of 6GB sparse file after extraction Bug marked as found in version 1.14.2-2. > close 374310 1.15.91-1 Bug#374310: tar: wrong size of 6GB sparse file after extraction 'close' is depr

Bug#374310: tar: wrong size of 6GB sparse file after extraction

2006-06-24 Thread Bas Zoetekouw
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

Bug#374310: tar: wrong size of 6GB sparse file after extraction

2006-06-18 Thread Joerg Delker
Package: tar Version: 1.15.1dfsg-3 Severity: critical Justification: causes serious data loss About a month ago, I tar-ed a 6GB sparse file (ntfsclone image) with "cjSf" options to get a nice 1.6GB tar.bz2 file. I've no exact information which tar version I used for that, but it was certainly f