[Pkg-octave-devel] [Reproducible-builds] Trying to fix random_buildpath_by_octave

Oliver Heimlich oheim at posteo.de
Sun Feb 7 12:46:55 UTC 2016


On 27.10.2015 18:36, Sébastien Villemot wrote:
> Le mardi 27 octobre 2015 à 13:40 +0100, Rafael Laboissiere a écrit :
>> I just committed a change to the octave-pkg-dev package for removing the 
>> -g option form the compilation flags [1]. The DOG packages seem to have 
>> reproducible builds now, at least as regards the binary files *.oct that 
>> are included in the package.
>>
>> @DOG: Please, review my changes and, if you think everything is ok, I 
>> will prepare a new version of octave-pkg-dev.
> 
> I am not totally happy with the solution of dropping the -g flag, but
> since we currently do not generate debug packages for octave-* packages,
> this is not a problem (but it will become one later, once .ddebs are
> implemented).
> 
> Still, if we want to go down that road, your last commit should be
> modified to use the flags generated by dpkg-buildflags (that way,
> DEB_BUILD_OPTIONS and other hardening features will be honored). For
> CFLAGS, you should use the result of:
> 
>  DEB_CFLAGS_MAINT_STRIP=-g dpkg-buildflags --get CFLAGS
> 
> (and similarly for other environment variables).
> 

What is the state of random build paths? The octave-interval package
does not build reproducible because of the random build paths, so I
guess the change isn't active yet.

https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/octave-interval.html

How about using a workaround and exchange the tempname function with
something that returns [tempdir]/oct-[counter]?

Oliver



More information about the Pkg-octave-devel mailing list