Bug#1144052: libnode137 regressed in reproducibility
Jochen Sprickerhof <[email protected]>
| Newsgroups | gmane.linux.debian.devel.bugs.rc |
|---|---|
| Organization | The Debian Project |
| Message-ID | <an1l4a2IcUJjswVr__40553.3601691545$1786603155$gmane$org@fenchel> |
Hi Jérémy, * Jérémy Lal <[email protected]> [2026-08-11 10:37]: >did it actually regress, or was the previous version failure ignored ? It regressed as the one in forky is reproducible: https://reproduce.debian.net/amd64/forky.html#libnode137 >I'm about to open an upstream bug report, because they want to make >their builds reproducible. > >The source of variation is likely to come from mksnapshot. >Anyone willing to look into this will want to search for >"predictable", "random_seed". I would be happy to help with this but currently I don't have the compute resources for such a big package. Cheers Jochen P.S.: Please note that bug authors are not automatically subscribed so please remember to Cc me.
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmp9ZeEACgkQW//cwljm lDN+ag//R5mBk89yLpkTPRlX/hDCyJB9ABYZ8vTJlTZ9z2n9VyG4D5SQxSVv639m /PKPGTCJsz3cRq4bqCJJ09UjrGEU9ng6286tLqLmFucYAtCTH8hICGs7ME/pL7YU GOrbJPSmGKAvbe5XKSMSm9Yj6mG73n1gASyMX1lykUVizEREZ+kV7kqNCr8pKKZ0 Mo6Hm7btJ9xgQubT9bUMMwUUYr0hunm6Kfo/29dTqdIB67EasNzpasYTRknnH0fT MCaFIziy9UWFBV3hozrCz+LDsOar5lWTEowitrPgiOPb6CNJy4upMPLIoVORtVil 11wcvZBuZLMiNVhVJME0lc/KKdUuUrKUfgHnZPVUP75AhfbLf/vrmrDPb8vcc1UT 1O4YjLc/ywftMHzdcfIng3s8G/qG0GFTgcZhU12pI1sJJjNQcgQIuXsZxzAx/y+R ZPgnhpA3juC93uBZgAfP6lgli3mlNPAKA2JV3vSDRygdjciYXoXiXp3Apn4GuOUx wkqxXhFxvRwNywE+LihEvlVrQ7tSju9VdBfWEvj3h43zXk+4nubU9LHASpcD8FRi QZSNvW++2NpcnQeXi9R5PybV5BJK/IUG6U68L4lukf13z3SvgT87E7XsyeExKd9W kthDTvhVoXadEQDQLlkckNZcXTN6pYNhzzhecDExefibdlQ9gS0= =n4bN -----END PGP SIGNATURE-----