Acknowledgement sent
to Holger Levsen <[email protected]>:
New Bug report received and forwarded. Copy sent to Reproducible builds folks <[email protected]>.
(Wed, 12 Apr 2023 19:54:04 GMT) (full text, mbox, link).
Package: reprotest
Version: 0.7.23
Severity: wishlist
Dear Maintainer,
<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
<vagrantc> h01ger: sure!
<h01ger> :) thanks
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
This too shall pass.
Acknowledgement sent
to Vagrant Cascadian <[email protected]>:
Extra info received and forwarded to list. Copy sent to Reproducible builds folks <[email protected]>.
(Fri, 08 Mar 2024 22:57:02 GMT) (full text, mbox, link).
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
:)
live well,
vagrant
Acknowledgement sent
to Vagrant Cascadian <[email protected]>:
Extra info received and forwarded to list. Copy sent to Reproducible builds folks <[email protected]>.
(Thu, 11 Apr 2024 23:18:02 GMT) (full text, mbox, link).
On 2024-03-08, Vagrant Cascadian wrote:
> 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
And merged in 0.7.27 ... which resolves the one specific issue mentioned
... are there any other must-haves we need to consider this bug closed?
Better documentation of how to actually do this? :)
live well,
vagrant
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.