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:scala-asm has been trying to migrate for
33 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. [End template] but it
doesn't, but the update_output [3] of the migration software helps us
find why:
trying: scala-asm
skipped: scala-asm (1, 2, 24)
     got: 41+0: a-15:a-6:a-2:i-17:l-1:p-0:r-0:s-0
     * amd64: scala-faux-build-depends
That's because of the newly added Breaks [4] which means src:scala can't
be build anymore because it Build-Depends on itself [5]. Either
src:scala-asm or src:scala needs fixing before scala-asm can migrate (or
src:scala needs to be removed from testing).

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Blocked packages can have impact on other packages,
which makes preparing for the release more difficult. The situation that
caused this bug report might even be the result of such an issue. We
expect maintainers to fix issues that hamper the migration of their
package in a timely manner. If your package in this situation due to
another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

This bug submission immediately closes the bug with the version in
unstable, so if that version or a later version migrates, this bug will
no longer affect testing. This bug is also tagged to only affect sid and
forky, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated. If you have any
comments with regards to the content or the process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=scala-asm
[3] https://release.debian.org/britney/update_output.txt
[4]
https://sources.debian.org/src/scala-asm/9.9.0-scala-1-1/debian/control#L19
[5] https://sources.debian.org/src/scala/2.11.12-6/debian/control#L20

Current text from [2]:
Migration status for scala-asm (5.2.0-scala-2-2 to 9.9.0-scala-1-1):
Will attempt migration (Any information below is purely informational)
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/s/scala-asm.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 33 days old (needed 5 days)

Hi,

I was checking

https://qa.debian.org/excuses.php?package=scala-asm

but it does not list any blocking reason.  Am I missing something?

Kind regards
    Andreas.

I: [2026-09-04T04:13:30+0000] - trying: scala-asm
I: [2026-09-04T04:13:30+0000] - skipped: scala-asm (23, 0, 216)
I: [2026-09-04T04:13:30+0000] -     got: 52+0: a-18:a-8:a-3:i-18:l-2:p-1:r-1:s-1
I: [2026-09-04T04:13:30+0000] -     * amd64: scala-faux-build-depends

i.e. migrating scala-asm would make scala unbuildable.

A little investigaton shows that:
- scala build-depends on itself and scala-asm
- scala-asm has "Breaks: scala (<< 2.12)"
- the scala version in unstable is 2.11.12-6, i.e. lower than 2.12

Regards,

Adam

Hi


Which was debugged and explained in bug https://bugs.debian.org/1142168

Paul

Thanks Paul and Andreas for raising this,

I starting working on migrating scala to 2.12 and scala-asm is on the roadmap of the needed dependencies.

I have packages prepared to make it possible, but I need sponsors to move them forward. Here is the status:

I can confirm Adam's diagnosis.

The fix in progress is a bump of src:scala from 2.11.12 to 2.12.21+ds. 2.12 is the last series buildable without sbt (sbt was removed from Debian in 2023, #1035929, and 2.12+ requires it upstream).

See this MR: https://salsa.debian.org/java-team/scala/-/merge_requests/2

The new scala embeds a transient 2.12.20 STARR seed as a build-time-only source input and self-hosts in a two-pass build; the seed is dropped after the first pass and scala self-bootstraps from the archive afterwards, so nothing prebuilt ships in the resulting binaries. It builds cleanly (sbuild unshare/unstable,
lintian --pedantic clean) against scala-asm 9.9.0.


It is still in draft pending review (the embedded seed needs a bootstrap exemption conversation with the FTP masters (not yet started), since prebuilt jars are present in the source for the first build even though they are not shipped).

Review and a sponsor upload would unblock this bug's underlying migration issue, besides the version.

This open the path to retire Scala 2.11 (scala-asm 9.x drops 5.x support), and the 14 reverse-dependencies of the old scala/scala-asm 5.x pair will need to follow; that is being tracked separately, and some of that work is already ongoing.

Best,

Juan

PS: I would appreciate any advice on how to deal with the FTP masters conversation for the bootstrap exemption.