Bug#1142168: src:scala-asm: fails to migrate to testing for too long

[Paul Gevers]

Source: scala-asm
Version: 5.2.0-scala-2-2
Severity: serious
Control: close -1 9.9.0-scala-1-1
Tags: sid forky
User: release.debian.org at packages.debian.org
Usertags: out-of-sync

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)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20260716/a6461823/attachment.sig>