Bug#1034311: reprotest: make it easier to compare against an existing build (eg from ftp.d.o)

2024-04-11 Thread Vagrant Cascadian
On 2024-03-08, Vagrant Cascadian wrote:
> On 2023-04-12, Holger Levsen wrote:
>>  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
>>YES
>>  e.g. there is no way to disable buidl path variations when 
>> comparing
>> against an arbitrary build
>>i'm reporting this as a bug to the bts, quoting your words here. 
>> (ok?)
>>  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


signature.asc
Description: PGP signature


Bug#1034311: reprotest: make it easier to compare against an existing build (eg from ftp.d.o)

2024-03-08 Thread Vagrant Cascadian
On 2023-04-12, Holger Levsen wrote:
>  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
>YES
>  e.g. there is no way to disable buidl path variations when 
> comparing
> against an arbitrary build
>i'm reporting this as a bug to the bts, quoting your words here. 
> (ok?)
>  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


signature.asc
Description: PGP signature


Bug#1034311: reprotest: make it easier to compare against an existing build (eg from ftp.d.o)

2023-04-12 Thread Holger Levsen
Package: reprotest
Version: 0.7.23
Severity: wishlist

Dear Maintainer,

 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
   YES
 e.g. there is no way to disable buidl path variations when comparing
against an arbitrary build
   i'm reporting this as a bug to the bts, quoting your words here. 
(ok?)
 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
  h01ger: sure!
 :) thanks


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

This too shall pass.


signature.asc
Description: PGP signature