* Reiner Herrmann <rei...@reiner-h.de> [2015-10-26 12:05]:


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.

Thanks, this is exactly the information that I needed. I think I found a fix for this issue by making a change in the octave-pkg-dev package [1].

Best,

Rafael

1. 
http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2015-October/011812.html

_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to