Closed GoogleCodeExporter closed 9 years ago
Without the file, there's nothing I can do about it.
Original comment by paracel...@gmail.com
on 26 Aug 2009 at 3:27
Ah. Unfortunately, it isn't a file I can give you, as it has customer
information and
such in it. Let me know if there's anything else I can give you.
Original comment by jamesmba...@gmail.com
on 27 Aug 2009 at 12:42
Did you create the file? Can you try to see if you can create another file in
the same way
that has the same problem?
Original comment by paracel...@gmail.com
on 27 Aug 2009 at 1:09
I wasn't the creator of the file. I have tried several things to try to
reproduce the
issue. I created a file with random text that was on the same scale as the
problem
file, and one that had all the same character. They both worked fine.
It looks like it's an issue with the specific file, or perhaps the specific
version
of bzip2 the creators used. After decompressing the original file with 1.6.1, I
re-compressed it with a local version of bzip2, and that copy decompressed fine
with
2.0. So I'm not really sure what the problem is.
Original comment by jamesmba...@gmail.com
on 27 Aug 2009 at 3:17
Very strange.
Actually, I have one idea what might have caused it. I'll look into that later
and report
back if I can reproduce anything.
Original comment by paracel...@gmail.com
on 27 Aug 2009 at 11:01
Incidentally, I don't know if this helps at all, but the part of the file that
does
get decompressed seems to be exactly one block, as it is exactly 900,000 bytes.
Original comment by jamesmba...@gmail.com
on 27 Aug 2009 at 2:33
bzip2 has an obscure feature where you can join several bzip2 files together to
form
one file. I just confirmed that those files don't work in The Unarchiver, and
fixed them.
It seems a lot like this could be a file like that, so I'm going to release
2.0.1 soon. Test
in that and tell me if it's fixed.
Original comment by paracel...@gmail.com
on 27 Aug 2009 at 9:46
All fixed! That must have been it. Thanks for the help!
Original comment by jamesmba...@gmail.com
on 28 Aug 2009 at 1:57
Original comment by paracel...@gmail.com
on 28 Aug 2009 at 2:12
Original issue reported on code.google.com by
jamesmba...@gmail.com
on 26 Aug 2009 at 3:59