Bug#1143570: src:openjdk-26: fails to migrate to testing for too long

Paul Gevers <[email protected]> Tue, 04 Aug 2026 11:16:24 +0200
Newsgroups gmane.linux.debian.devel.bugs.rc
Message-ID <178583498476.211954.14015913775840011858__2131.13590595952$1785835161$gmane$org@debian.org>
Source: openjdk-26
Version: 26+35-2
Severity: serious
Control: close -1 26.0.2+10-2
Tags: sid forky
User: [email protected]
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:openjdk-26 has been trying to migrate for 109 days [2], h=
ence this bug report. The current output of the migration software for this p=
ackage is copied to the bottom of this report and should list the reason why =
the package is blocked.

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 u=
nstable. Blocked packages can have impact on other packages, which makes prep=
aring for the release more difficult. The situation that caused this bug repo=
rt might even be the result of such an issue. We expect maintainers to fix is=
sues that hamper the migration of their package in a timely manner. If your p=
ackage in this situation due to another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new bugs, th=
ere 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 affec=
t 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 bey=
ond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated. If you have any comments wi=
th 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=3Dopenjdk-26

Current text from [2]:
Migration status for openjdk-26 (26+35-2 to 26.0.2+10-2): BLOCKED: Maybe temp=
orary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
=E2=88=99 =E2=88=99 Missing build on loong64
=E2=88=99 =E2=88=99 Autopkgtest deferred on loong64: missing arch:loong64 bui=
ld
=E2=88=99 =E2=88=99 Autopkgtest for libreoffice/4:26.2.4.2-2: amd64: Pass, ar=
m64: Test triggered (failure will be ignored), armhf: Test triggered (failure=
 will be ignored), i386: Test triggered (failure will be ignored), ppc64el: P=
ass, riscv64: Pass, s390x: Pass
=E2=88=99 =E2=88=99 Autopkgtest for openjdk-26/26.0.2+10-2: amd64: Pass, arm6=
4: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el=
: Test triggered (failure will be ignored), riscv64: Test triggered (failure =
will be ignored), s390x: Pass
=E2=88=99 =E2=88=99 Lintian check waiting for test results on loong64 - info
Additional info (not blocking):
=E2=88=99 =E2=88=99 Piuparts tested OK - https://piuparts.debian.org/sid/sour=
ce/o/openjdk-26.html
=E2=88=99 =E2=88=99 Not reproduced on amd64 (not a regression): openjdk-26-jdk
=E2=88=99 =E2=88=99 Not reproduced on arm64 (not a regression): openjdk-26-jdk
=E2=88=99 =E2=88=99 Reproduced on armhf - info
=E2=88=99 =E2=88=99 Reproduced on i386 - info
=E2=88=99 =E2=88=99 11 days old (needed 5 days)