Hi Rafael, On Sun, Oct 25, 2015 at 09:09:54PM +0100, Rafael Laboissiere wrote: > I am trying to fix the issue identified as random_buildpath_by_octave [1], > which affects several packages maintained by the Debian Octave Group [2]. Thanks for looking into it! > I need to know how the "variation of the build id", mentioned in issue > description, is detected. Is it done from the build log? If you look at the page of an affected package [1], you can find a diff of the logs between both build [2]. There you won't find the build id, but the cause of the binary variation: > -mkdir (/tmp/oct-RnOahg) > -Copying directory (., /tmp/oct-RnOahg) > -make[1]: Entering directory '/tmp/oct-RnOahg/src' > +mkdir (/tmp/oct-KZzyZE) > +Copying directory (., /tmp/oct-KZzyZE) > +make[1]: Entering directory '/tmp/oct-KZzyZE/src' In the diff of the compiled binary packages [3] you can then see that the "Build ID" is differing: > │ │ │ │ │ - Build ID: 5f46757a2de5cce2303368e1b8490fabc2278a5f > │ │ │ │ │ + Build ID: fed8cdbc88dc2ce89aecf63b89d0e7083d987aa0 I hope this helps you. Kind regards, Reiner [1]: https://reproducible.debian.net/rb-pkg/unstable/amd64/octave-control.html [2]: https://reproducible.debian.net/logdiffs/unstable/amd64/octave-control_2.8.5-1.diff.gz [3]: https://reproducible.debian.net/dbdtxt/unstable/amd64/octave-control_2.8.5-1.debbindiff.txt
Attachment:
signature.asc
Description: Digital signature