(Resent to the list, my reply only went to the bug and to Simon.)

Hi Simon,

Thanks! I prefer a team upload. I also asked to join the Java team
(https://lists.debian.org/debian-java/2026/10/msg00020.html), but got no
answer yet.

The steps, in order:

1. scala 2.12.21+ds3-1, from
   https://salsa.debian.org/java-team/scala/-/merge_requests/2.
   As you know, this first upload goes with binaries and will not migrate.
   It is built with the pkg.scala.stage0 profile, see debian/README.source.

2. scala 2.12.21+ds3-2, source-only, from
   https://salsa.debian.org/java-team/scala/-/merge_requests/3, to upload
   once step 1 is in unstable. With it, scala and scala-asm can reach
   testing before the autoremoval on 2026-11-01.

3. pilon and plm: https://bugs.debian.org/1152082 and
   https://bugs.debian.org/1152084, each with its MR.

4. scala-xml-2.12 and scala-parser-combinators-2.12 (NEW,
   https://bugs.debian.org/1149688 and https://bugs.debian.org/1149687),
   then latexdraw: https://bugs.debian.org/1152108. latexdraw also needs
   jinput to migrate: https://bugs.debian.org/1069434, with
   https://salsa.debian.org/java-team/jinput/-/merge_requests/2.

No binNMUs are needed. The other reverse dependencies you listed (jawn,
json4s, scopt, sbt-launcher-interface, sbt-serialization, scala-pickling,
scala-tools-sbinary, scala-xml and scala-parser-combinators) are 2.11
libraries of the old sbt 0.13 stack. After step 4 nothing uses them, and
I will file removal requests for them.

Best regards,
Juan

Reply via email to