Rakudo Packages for 2024.08 Release (was: Re: Taking over Maintenance)

[Dominique Dumont]

Hi

On Thursday, 26 September 2024 02:53:08 CEST Timo Paulssen wrote:
> I have merge requests for moarvm, nqp, and rakudo in place for
> making 2024.08 release packages.

I've added some comments in the merge requests on salsa. The main issue is 
master or debian/sid are targeted instead of debian/experimental (to be 
honest, this branch was missing in nqp and rakudo repos).
 
> There is one lintian error, which is thankfully just about the version
> in the changelog being improper:
> 
> https://salsa.debian.org/timotimo-guest/moarvm/-/pipelines/737259/test_repor
> t?job_name=lintian
> 
> maintainer-upload-has-incorrect-version-number
> 2024.08+dfsg-1~1.gbp07b151+salsaci+20240925+27 [debian/changelog:1]

I will sort this out before uploading to experimental

> I am glad to report, that reprotest is also giving me a positive result
> for the default settings in the salsa CI:

That's a great achievement !

> Also, I think there is not yet a debin/sid branch to merge into. Easy to
> fix, of course.

You mean debian/experimental.

We'll merge all this to debian/sid (and upload to unstable) once we have the 
greenlight from debian release team to trigger the rebuild of all Raku 
modules. But first, we must make sure that everything is fine in Debian 
experimental.

> Here somehow the version number lintian saw in the changelog must have
> been satisfactory? But it couldn't find a signature for the original
> tarball, which I haven't investigated yet.

Let's not worry too much about version number before we're ready to upload to 
experimental. I'll check this at that time.

> Unfortunately I was not yet able to make reprotest happy for rakudo.

ok, one step at a time.

> The merge request is aimed at the debian/sid branch, but I think it's
> safe to hard-reset it to the head of the merge request branch.

I'd rather use debian/sid branch to upload to debian/unstable (aka sid). 
Otherwise creating a patch release of rakudo is messy.

To target debian/experimental instead of debian/sid (or master), you should:
- recreate the merge commit from upstream 2024.08 in debian/experimental
- rebase a subset (or cherry-pick) all the commits of your PR.

> The next rakudo release is literally roughly a day away, but I think it
> would still be a useful learning exercise for me to have the package for
> 2024.08 built and uploaded.

Uploaded in experimental ?  Sure. We'll see for unstable, because I'd rather 
avoid 2 transitions (where all raku modules are rebuilt) in a short time 
frame.

>   raku-meta6
> 
> I have not yet looked at what's wrong with this package. I have also not
> exactly checked out what the ramifications are for blocked packages in
> the scheme by which rakudo and the module packages are moved along.

All raku package depending on raku-meta6 are blocked. Otherwise, dependencies 
cannot be resolved in Debian testing.

All the best

Dod