Bug#908365: Package fails to build reproducibly

[Vagrant Cascadian]

On 2018-09-10, Michael Biebl wrote:
> Am 10.09.18 um 19:22 schrieb Chris Lamb:
>>> Now, I could try and convince upstream to not embed ABS_BUILD_DIR into
>>> the binary and maybe let the build system pass the build dir as env var.
>>> This would make those test-binaries a bit more cumbersome to use though,
>>> because you'd have to manually set the env var if you directly execute
>>> the test by hand.
>> 
>> Hm, could you not install the test data to /usr/systemd/private/path>
>> whatever and then make the tests default to this,
>
> The binaries have a builtin check, which tests if they are executed from
> the build directory, and if so, use the data files from the build
> directory. Otherwise they use the datafiles from
> /usr/lib/systemd/tests/testdata/
>
>>  overiddable by the
>> said env var? That would avoid the ugly requirement to set it manually
>> at the very least.
>
> If you run the test directly from the build directory, it's reasonable
> to assume that you actually want to use the data files from the build
> directory as well and not the ones from the installed system.
> Atm the binaries auto-detect that by encoding the build directory into
> the binary.

Is it plausible to strip the embedded build directory information out of
the test binaries with the binaries shipped in the package, since they
will almost certainly not have access to the original build directory,
and it interferes with the reproducibility of the test package...

Alternately, run two builds of the test binaries, one during the build
which contain the embedded build dir, and a second time setting the
value to match the shipped package.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180912/23772cea/attachment-0002.sig>