[keeping Domenico in CC until he asks to be dropped]

> │ │ │ │ -    Build ID: 6f3f14da239d0b68ba179ee7a2f2570c4d970db0
> │ │ │ │ +    Build ID: c68caf4dba0ea46c05dddf9405bda4290c6ceaa6

I was under the (possibly-false!) impression that this was a symptom
rather than anything like a cause.

In other words, this might be just the same way of saying that (for
example) the checksums of the .debs differ; well of course they do;
the package is not unreproducible yet!

To be clear, I am not saying that the package is reproducible or this
warrants no further investigation, it just might be a red herring to
assume it was 100% debug symbol related. Just throwing that out there
in case it might save you some unnecessary brain cycles.

If it helps, the first thing I would check is how exactly one can get
this "Build ID" to vary; is it always the same values with those
specific build-paths for example, or is it entirely deterministic?
That would quickly eliminate a whole plethora of incorrect avenues.

> There's also a page listing the issues on tests.reproducible-builds.org,
> but I can't access that right now...

For completeness, this is now back:

  https://tests.reproducible-builds.org/debian/index_issues.html


Best wishes,

-- 
      ⚫
    ⬋   ⬊      Chris Lamb
   ⚫     ⚫    reproducible-builds.org
    ⬊   ⬋
      ⚫

_______________________________________________
Reproducible-builds mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to