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

Timo Paulssen timo+deb at wakelift.de
Sun Oct 6 15:49:47 BST 2024


Hi List,

(though this question is kind-of aimed at Dominique)

I think we had an upload of rakudo, which is still giving results that 
change from build to build. In particular, the precompiled rakudo source 
files.

I believe this is what's caused this bug for example:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083145

when looking at the full logs folder:

https://people.debian.org/~sanvila/build-logs/202410/

we can see that there is no build here for raku-tap-harness, and in the 
installation part of the build log

https://people.debian.org/~sanvila/build-logs/202410/prove6_0.0.12-7_amd64-20241002T103636.769Z

at around the one quarter mark, we see this version of raku-tap-harness 
being installed:

Get:90 http://deb.debian.org/debian sid/main amd64 raku-tap-harness 
amd64 0.3.8-2+b2 [145 kB]

This is the same version I get when I try to `gbp buildpackage` inside 
my local checkout of prove6.

By doing a dummy snapshot build of raku-tap-harness and raku-getopt-long 
like this:

     gbp dch -S
     git commit -a -m 'dummy snapshot build'
     gbp buildpackage

and then providing the packages it created to sbuild like this:

gbp buildpackage 
--extra-package=/home/timo/raku/build-area/raku-tap-harness_0.3.8-3~1.gbp60c7b8_amd64.deb 
--extra-package=/home/timo/raku/build-area/raku-getopt-long_0.4.2-2~1.gbp83c8cd_amd64.deb

I now get a working build.

So it looks like if you install something from the raku suite of 
packages on debian unstable right now, you get something that's broken. 
And indeed,

podman run -u root -it --rm library/debian:unstable-slim /bin/bash -c 
'apt-get update; apt-get install -y prove6; prove6'

results in the dreaded

     Missing or wrong version of dependency 'gen/moar/BOOTSTRAP/v6c.nqp'

So I think the solution to these errors would be to rebuild all raku 
packages.

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?

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.

Thanks,
   - Timo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-rakudo-devel/attachments/20241006/b75b97dc/attachment.htm>


More information about the Pkg-rakudo-devel mailing list