<vagrantc> i guess reprotest maybe should grow an option to do
--control-build /path/to/packages/
--vary=build_path=/use/this/build/path ...
to make it easier to use reprotest to compare against an existing build
<h01ger> YES
<vagrantc> e.g. there is no way to disable buidl path variations when comparing
against an arbitrary build
<h01ger> i'm reporting this as a bug to the bts, quoting your words here. (ok?)
<vagrantc> reprotest can control it's own builds ... but if i want to use reprotest
against the archive packages or an sbuild
or pbuilder build package ... it will always have a different build path
On 2023-04-12, Holger Levsen wrote:
<vagrantc> i guess reprotest maybe should grow an option to do
--control-build /path/to/packages/
--vary=build_path=/use/this/build/path ...
to make it easier to use reprotest to compare against an existing build
<h01ger> YES
<vagrantc> e.g. there is no way to disable buidl path variations when comparing
against an arbitrary build
<h01ger> i'm reporting this as a bug to the bts, quoting your words here. (ok?)
<vagrantc> reprotest can control it's own builds ... but if i want to use reprotest
against the archive packages or an sbuild
or pbuilder build package ... it will always have a different build path
Forgot about this bug, but I have since implemented a proof-of-concept
of this:
https://salsa.debian.org/reproducible-builds/reprotest/-/commits/wip-specify-build-path?ref_type=heads
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 07:31:25 |
Calls: | 6,706 |
Files: | 12,236 |
Messages: | 5,350,636 |