Reproducibility requirement

[Timo Paulssen]

Hi Dominique,

Thanks for the heads-up.

With some work I've done a few months ago, nqp and rakudo should be 
reproducible already. I believe this should be the case for the latest 
rakudo we have in debian.

I will take a look at the reproducibility status of the packages soon.

We still need to be careful, of course. When there are any changes to 
actual nqp or raku code inside rakudo, the compiler ID must change, and 
packages will need to be precompiled anew.

I haven't looked at the reproducibility of module packages yet. There 
are modules out there in the ecosystem that do stuff in a build script, 
which is very easy to accidentally make not-reproducible. I'm not sure 
if any debian packages have build scripts in them, however.

Kind Regards
   - Timo

On 5/10/26 10:42, Dominique Dumont wrote:
> Hi
>
> Here's a new requirement for Debian packages:
>
> On Sunday, 10 May 2026 06:47:30 Central European Summer Time Paul Gevers
> wrote:
>> Reproducibility
>> ===============
>>
>> Aided by the efforts of the Reproducible Builds project [1], we've decided
>> it's time to say that Debian must ship reproducible packages. Since
>> yesterday, we have enabled our migration software to block migration of new
>> packages that can't be reproduced [2] or existing packages (in testing)
>> that regress in reproducibility.
> IIRC, the main problem to get reproducible rakudo packages is the compiler id
> which is not reproducible.
>
> This will need to be improved for newer rakudo packages to be available in
> Debian testing  and future Debian releases.
>
> All the best
>
> _______________________________________________
> Pkg-rakudo-devel mailing list
> Pkg-rakudo-devel at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rakudo-devel