Bug#1143569: src:node-yarnpkg: fails to migrate to testing for too long

Source: node-yarnpkg
Version: 4.1.0+dfsg-6
Severity: serious
Control: close -1 4.1.0+dfsg-7
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:node-yarnpkg has been trying to migrate for 36 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.

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=3Dnode-yarnpkg

Current text from [2]:
Migration status for node-yarnpkg (4.1.0+dfsg-6 to 4.1.0+dfsg-7): BLOCKED: Re=
jected/violates migration policy/introduces a regression
Issues preventing migration:
=E2=88=99 =E2=88=99 Updating node-yarnpkg would introduce bugs in testing: #1=
141793
=E2=88=99 =E2=88=99 Autopkgtest for jupyterlab/4.4.10+ds1+~3.1.0+~0.16.6+~cs1=
.4.4-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression =E2=99=BB (re=
ference =E2=99=BB), loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regre=
ssion =E2=99=BB (reference =E2=99=BB)
=E2=88=99 =E2=88=99 Autopkgtest for node-yarnpkg/4.1.0+dfsg-7: amd64: Pass, a=
rm64: Pass, armhf: Pass, i386: Pass, loong64: No tests, superficial or marked=
 flaky =E2=99=BB, ppc64el: Pass, riscv64: Pass, s390x: Pass
=E2=88=99 =E2=88=99 Build-Depends(-Arch): node-yarnpkg node-tar
=E2=88=99 =E2=88=99 Depends: node-yarnpkg node-tar
Additional info (not blocking):
=E2=88=99 =E2=88=99 Updating node-yarnpkg will fix bugs in testing: #1140994
=E2=88=99 =E2=88=99 Piuparts tested OK - https://piuparts.debian.org/sid/sour=
ce/n/node-yarnpkg.html
=E2=88=99 =E2=88=99 Reproduced on amd64 - info
=E2=88=99 =E2=88=99 Reproduced on arm64 - info
=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 35 days old (needed 5 days)