How do I get module packages properly rebuilt after a rakudo upload?

[Dominique Dumont]

On Sunday, 6 October 2024 16:49:47 CEST Timo Paulssen wrote:
> Instead of waiting for the packages in experimental to be built and moved (I
> forgot the term, but it's different from migration) into unstable, should
> we do that sooner?

It's called a transition. Triggering a transition (hence uploading to unstable) will probably be faster than rebuilding all packages. 

> How should I treat the bugs in BTS that have the "missing or wrong version
> of dependency" error? In a way, they are both correct and incorrect.

IIRC, all these issues stem from unpredictable rakudo compiler Id.

I've tried several tricks but, in the end, rakudo's compiler id changes in unpredictable ways that trigger unwanted precompilation of modules and the conflicts between inter dependant modules.

The problem is explained there:
https://wiki.debian.org/RakuPreCompProposal

One of the attempt to fix compiler id is there, unfortunately, this is not enough:
https://salsa.debian.org/perl6-team/rakudo/-/blob/master/debian/patches/fix-compiler-id

There's a Git issue on that topic with the whole history:
https://github.com/rakudo/rakudo/issues/5099

There's one lead that may need to be followed up:
https://github.com/rakudo/rakudo/issues/5099#issuecomment-1515132194

Until rakudo compiler Id becomes reproducible, shipping precompiled modules will be messy, be it with a transition or by manual upload of packages.

All the best