Package: release.debian.org Severity: normal X-Debbugs-Cc: rak...@packages.debian.org Control: affects -1 + src:rakudo User: release.debian....@packages.debian.org Usertags: transition
Hi rakudo and its sibling packages (moarvm and nqp) have an API that change at every release. This requires a rebuild of all raku modules when a new rakudo is uploaded. No other packages outside of raku modules are affected. Although the situation is quite fluid, I believe that raku modules will build fine even though some of them are FTBS now. Anyway, Timo Paulssen is the new maintainer for all rakudo packages. He's part od upstream team so I expect he will take care of any problem that may arise (and I will sponsor his work). rakudo transitions are tracked by a permanent tracker: https://release.debian.org/transitions/html/rakudo.html Can I upload moar, nqp and rakudo to unstable ? All the best Ben file generated from bts questions: title = "rakudo"; is_affected = .depends ~ "raku-api-2022.12+af50a328" | .depends ~ "raku-api-2024.09+b2021349"; is_good = .depends ~ "raku-api-2024.09+b2021349"; is_bad = .depends ~ "raku-api-2022.12+af50a328";
