Bug#1003919: apulse: reproducible-builds: BuildId differences triggered by RPATH

2022-01-28 Thread Miroslav Kratochvil
> > Should we release this as 0.1.13-2 ? > > Well, of course I'm biased towards reproducible builds... so my answer > is yes! :) True, let's do it. I'll have the upload close this bug so that this gets visibly solved. :] -mk

Bug#1003919: apulse: reproducible-builds: BuildId differences triggered by RPATH

2022-01-28 Thread Vagrant Cascadian
On 2022-01-26, Miroslav Kratochvil wrote: > Many thanks for reporting, I pushed this to github repo. I will update > debhelper number when it's out of experimental. > > Should we release this as 0.1.13-2 ? Well, of course I'm biased towards reproducible builds... so my answer is yes! :) But it is

Bug#1003919: apulse: reproducible-builds: BuildId differences triggered by RPATH

2022-01-26 Thread Miroslav Kratochvil
Hello! Many thanks for reporting, I pushed this to github repo. I will update debhelper number when it's out of experimental. Should we release this as 0.1.13-2 ? Best, -mk

Bug#1003919: apulse: reproducible-builds: BuildId differences triggered by RPATH

2022-01-17 Thread Vagrant Cascadian
Source: apulse Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstabl