1 |
On 06/27/10 20:33, Brian Harring wrote: |
2 |
> On Sun, Jun 27, 2010 at 01:08:58PM +0200, Enrico Weigelt wrote: |
3 |
>> * Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> schrieb: |
4 |
>> |
5 |
>>>> Well, at least for tar, I've experienced no problem here yet. |
6 |
>>>> But: true, it might change between tar versions. |
7 |
>>> |
8 |
>>> The main offender is the compression program, not tar. |
9 |
>> |
10 |
>> hmm, I'm exclusively using bzip2 and never had these problems |
11 |
>> yet. maybe it depends on the compressor type. |
12 |
> |
13 |
> http://www.gentoo.org/proj/en/glep/glep-0025.html#the-problem-in-detail |
14 |
> |
15 |
> Note also that bzip2 had another change in output after that |
16 |
> release- my memory is failing me a bit, but it was roughly a |
17 |
> a reduction of their hash size to fix a CVE- either way, same thing, |
18 |
> differing output. |
19 |
Are you thinking about |
20 |
"bzip2 version 1.0.2 worked with huffman codes with a length of up to 20 |
21 |
bits. Unfortunately the Author of bzip2, Julian Seward, changed this in |
22 |
the new version 1.0.3 - it uses only a maximum length of 17 bits now. " |
23 |
(Quoted from http://linux01.gwdg.de/~nlissne/bugsandproblems.html ) ? |