I just want to give a heads up that: > Version 2024.09+dfsg-3 of moarvm is marked for autoremoval > from testing on Tue 22 Apr 2025. > > The removal of moarvm will also cause the removal of (transitive) > reverse dependencies: > dh-raku, nqp, prove6, raku, raku-file-find, raku-file-which, > raku-getopt-long, raku-hash-merge, raku-json-class, raku-json-fast, > raku-json-marshal, raku-json-name, raku-json-optin, raku-json-unmarshal, > raku-librarycheck, raku-license-spdx, raku-log, raku-meta6, raku-readline, > raku-tap-harness, raku-test-meta, raku-uri, raku-zef, rakudo. > > You should try to prevent the removal by fixing these RC bugs.
This mail will bump the autoremoval date a bit in to the future, but please note that due to the current freeze status, removal from trixie will likely be permanent if it is going through. I've (indirectly) asked what causes this on -release irc. >From there i leave this following hints: > Somebody needs to request removal of nqp, etc. on arm*. > from unstable. That's #debian-ftp territory. On Sun, 9 Mar 2025 16:55:03 +0100 Paul Gevers <elb...@debian.org> wrote: > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:moarvm has been trying to migrate for 34 > days [2], hence this bug report. The current output of the migration > software for this package is copied to the bottom of this report and > should list the reason why the package is blocked.
