Bug#1006274: transition: rakudo

[Sebastian Ramacher <sramacher@debian.org>]

Control: tags -1 confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/rakudo.html

On 2022-02-22 09:45:35, M. Zhou wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> 
> Dear release team,
> 
> Rakudo upstream has released 2022.02 version, and I have uploaded it to
> experimental. In the past few weeks the architecture of the raku-*
> packages has been changed to any, which means binnmus should be possible.
> Shall we start the rakudo 2022.02 transition?

Please go ahead

> BTW, since we have a permanent transition tracker
> https://release.debian.org/transitions/html/rakudo.html
> Do we have to request for transition slot every time?

Yes. As the current setup requires a lockstep transition, this is
ideally coordinated with us. We want to avoid conflicts between such
lockstep transitions and other transition.

In any case you would need to ask for binNMUs anways. The best place to
coordinate those rebuilds is a tranistion bug.

Cheers

> 
> Thanks!
> 
> Ben file:
> 
> title = "rakudo";
> is_affected = .depends ~ "raku-api-2021.12" | .depends ~ "raku-api-2022.02";
> is_good = .depends ~ "raku-api-2022.02";
> is_bad = .depends ~ "raku-api-2021.12";
> Thank you for using reportbug
> 

-- 
Sebastian Ramacher