| 1 |
Miroslav Rovis wrote: |
| 2 |
> On 170502-10:33+0200, Raffaele Belardi wrote: |
| 3 |
>> Miroslav Rovis wrote: |
| 4 |
>>> gzip apparently inconsistent behavior occupies the most part of the report on |
| 5 |
>>> inconsistencies here (esp. the script make_gzip_archives_consistent.sh). |
| 6 |
>> |
| 7 |
>> Checked on my system, same behaviour, looking inside the gzip file you see why. I used |
| 8 |
>> shed but strings is easier: |
| 9 |
>> |
| 10 |
>> $ strings eix-installed-after_1.gz |
| 11 |
>> eix-installed-after_1 |
| 12 |
>> ... |
| 13 |
>> |
| 14 |
>> $ strings eix-installed-after_2.gz |
| 15 |
>> eix-installed-after_2 |
| 16 |
>> ... |
| 17 |
>> |
| 18 |
>> gzip stores the filename in the compressed file so the files differ. |
| 19 |
> |
| 20 |
> No, it doesn't, on my system. Did you really check the files: |
| 21 |
> https://lists.gt.net/engine?do=post_attachment;postatt_id=51651;list=gentoo |
| 22 |
> https://lists.gt.net/engine?do=post_attachment;postatt_id=51652;list=gentoo |
| 23 |
> (these should download as eix-installed-after_1.gz former and eix-installed-after_2.gz the latter)? |
| 24 |
> |
| 25 |
> And they have these SHA256: |
| 26 |
> |
| 27 |
> fff6f3f0f07c863fee6962379f063f742578569fd13fcee3df9161b4a6d99aa7 eix-installed-after_1.tar.gz |
| 28 |
> b88cd07885fbdc2235c9c64be7d02aa9ace7661cc2fce07909355e369366b408 eix-installed-after_2.tar.gz |
| 29 |
> |
| 30 |
> If you did check those files, and there are the strings you say, at what |
| 31 |
> byte, the start, and the end... Really don't know how you got that... |
| 32 |
|
| 33 |
I did not use your files, I re-generated them on my system based on the |
| 34 |
/usr/bin/eix-installed-after installed on my system, as you suggested. The command I used |
| 35 |
was plain gzip, not tar, since the difference in the files appears to come from the gzip |
| 36 |
execution. |
| 37 |
|
| 38 |
I just checked your files: |
| 39 |
|
| 40 |
$ cmp -bl gzip_buggy.txt_1.tar.gz gzip_buggy.txt_2.tar.gz |
| 41 |
5 7 ^G 12 ^J |
| 42 |
|
| 43 |
They differ in byte 5 which, according to the link I posted, is inside the MTIME field. |
| 44 |
Looks to me that this gzip issue is a non-issue. |
| 45 |
|
| 46 |
Regarding the other issues, maybe someone else will have the time to go through the |
| 47 |
complete email, even the abridged one you re-sent is too much for me. Or maybe if you |
| 48 |
could concentrate on one issue at a time only... |
| 49 |
|
| 50 |
raffaele |
Archives