reproduceiable issue on -dbgsym package

Vagrant Cascadian vagrant at reproducible-builds.org
Mon May 6 17:33:25 BST 2024


On 2024-05-06, Bo YU wrote:
> I have one package aemu[0] and its reprotest[1] test failed. However
> from the log online, I did not find any value cluster to fix the
> issue. So I use `reprotest` locally:

My guess would be build paths.

You could use reprotest --auto-build to systematically search for what
type of issue it is (e.g. first test only timestamps, then test only
build path, etc.). At the end it reports which variations triggered the
reproducibility issue.

If it is build paths, since it is a cmake project, you might try setting
from debian/rules:

  -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON

This documents the issue a bit more:

  https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html


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/reproducible-builds/attachments/20240506/14d6f003/attachment.sig>


More information about the Reproducible-builds mailing list