Three bytes in a zip file

Chris Lamb chris at reproducible-builds.org
Fri Mar 8 11:16:06 UTC 2024


Hey Fay,

Oh this is great work! So, using your tool, did you manage to solve the
underlying non-determinism? :)

Based on the output (which labels the field as an 'extra atime' or
similar), it seems like you've managed to work out which part of your
toolchain is making the build reproducible — or am I being too
optimistic?


Best wishes,

Chris


ps. Separate to that, how amenable would you be to working with me getting
    this extra .ZIP metadata support built directly into diffoscope at
    some point…?



Fay Stegerman wrote:

> * Larry Doolittle <larry at doolittle.boa.org> [2023-04-06 23:59]:
>> Do you know of any tooling that can help decode zip file contents in general?
>
> I know this thread is almost a year old now, but I finally got to my backlog
> working on diff-zip-meta.py [1], which is a tool specifically intended to
> elucidated differences in ZIP/APK metadata.  And as of today, the master branch
> supports showing the kind of timestamp differences you reported in
> human-readable form, not just as a difference in the raw data:
>
> $ diff-zip-meta foo.zip bar.zip
> --- foo.zip
> +++ bar.zip
> entry foo:
>   extra (entry):
> -   55540900035164ea655164ea6575780b000104e803000004e8030000
> +   55540900035164ea655464ea6575780b000104e803000004e8030000
> - extra (entry) atime=2024-03-08 01:05:21
> + extra (entry) atime=2024-03-08 01:05:24
>
> - Fay
>
> [1] https://github.com/obfusk/reproducible-apk-tools#diff-zip-metapy


-- 
      o
    ⬋   ⬊      Chris Lamb
   o     o     reproducible-builds.org 💠
    ⬊   ⬋
      o



More information about the rb-general mailing list