Hi Emmanuel, Sounds good, let's go with your plan. I already have the no-sbt 2.12 build and can move it into the two-pass embedded-seed proposal.
- One thing to keep in mind: step 1 (dropping scala-asm 5.x) retires Scala 2.11, which has the 14 source reverse-deps. They will need rebuilding, porting, or removal. Your PLM PR will cover the main dependency of the old 2.11, and most of the rest already dropped Scala upstream, so it should be manageable. New MRs: scala-asm: https://salsa.debian.org/java-team/scala-asm/-/merge_requests/4 Scala: Bumped to 2.12.21 with your approach: New MR https://salsa.debian.org/java-team/scala/-/merge_requests/2 Clean with sbuild + lintian --pedantic + autopkgtest. Please, have a look when you have some time, Juan Best, Juan -------- Original Message -------- On Friday, 06/12/26 at 17:58 Emmanuel Bourg <[email protected]> wrote: Le 12/06/2026 à 16:15, Juan M. Méndez Rey a écrit : > So, going straight to the point. > Cleanest order to start, no exemption needed: > > 1. scala-asm coexistence (5.2.0 for 2.11 + 9.9.0 for 2.12) > No new binary names, so no NEW queue: > > https://salsa.debian.org/java-team/scala-asm/-/merge_requests/3 > > 2. scala -> scala-2.11 rename (built + install tested locally, with a scala > metapackage) > > https://salsa.debian.org/java-team/scala/-/merge_requests/1 > > 2.1 plm, in the meanwhile, while your PR gets merged. > plm switches Build-Depends to "scala-2.11 | scala" so it keeps getting 2.11 > during and after the transition (NMU): > > https://salsa.debian.org/java-team/plm/-/merge_requests/3 > > 3. sbt-util-interface (#1139638): pure-Java leaf, ready for NEW: > https://salsa.debian.org/mendezr/sbt-util-interface > > jline3 is a Scala 2.13 thing, independent of 2.11, so it needn't hold this > up. But in the meanwhile, I answered about that here, asking for your input. > https://salsa.debian.org/java-team/jline3/-/merge_requests/3#note_769369 > > The scala-2.12-bootstrap "seed" is the only piece needing the "exemption > talk", as we call it, with the ftp masters. What about the following steps: 1. Upgrade scala-asm to 9.x, do not keep 5.x 2. Inject the scala 2.12 jars in the existing scala package and build Scala 2.12 with a two pass build (1st with the prebuilt jars, the second without) 3. Update PLM 4. Package the sbt stuff That would skip the scala-2.12-bootstrap package Emmanuel Bourg
