Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition X-Debbugs-Cc: rak...@packages.debian.org Control: affects -1 + src:rakudo
Dear release team, We would like to start the transition for rakudo, updating rakudo to the latest version in unstable. It involves three packages, src:moarvm, src:nqp, and src:rakudo. They are built successfully in experimental. The s390x buildd is super slow this week -- I waited for a week and it has not started a build yet.... All other architectures look good. This upload also aims to trigger rebuild for all reverse dependencies to mitigate some issues about the compiler ID. Specifically, the pre-compiled cache shipped in reverse dependencies relies on a matching compiler ID. Hence, we added the compiler ID into the virtual package to ensure cache compatibility: raku-api-2022.12+e556a5c0 The compiler ID will change when code is modified. Albeit adding the compiler ID may not sound like an ideal solution, this seems like what we can do before the freeze. Ben file: title = "rakudo"; is_affected = .depends ~ "raku-api-2022.07" | .depends ~ "raku-api-2022.12+e556a5c0"; is_good = .depends ~ "raku-api-2022.12+e556a5c0"; is_bad = .depends ~ "raku-api-2022.07"; Thank you for using reportbug
