• Bug#1034311: reprotest: make it easier to compare against an existing b

    From Vagrant Cascadian@21:1/5 to Holger Levsen on Sat Mar 9 00:00:01 2024
    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

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZeuWygAKCRDcUY/If5cW qsZQAP9XrXWQI8VxTp8NYJzznEJSGuBxpLOpA0AxEzfSJgOZ2gEA1P0QO3NLSYk8 uzVZRMdmbyr1TBKKkei51rpz5ojLNAw=wlKZ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Vagrant Cascadian@21:1/5 to Vagrant Cascadian on Fri Apr 12 01:20:01 2024
    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

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZhhu+gAKCRDcUY/If5cW qtIDAQC+FtPdmG6e1yAVoMPaH1yWvxGCLQa0eyuBAKxJq3+lCQEAqLqZsaUyBXOq nUouzQqe6PdfJTPFyMvs92r6PuwINQ0à4C
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)