[Debian-med-packaging] Bug#1125170: src:seqan2: fails to migrate to testing for too long

[Paul Gevers]

Source: seqan2
Version: 2.4.0+dfsg-16
Severity: serious
Control: close -1 2.5.2-1
Tags: sid forky
User: release.debian.org at packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1121732

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:seqan2 has been trying to migrate for 38 
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 unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or its 
(reverse-)dependencies. We expect maintainers to fix issues that hamper 
the migration of their package in a timely manner.

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 and has only been sent 
manually. 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=seqan2

Current text from [2]:
Migration status for seqan2 (2.4.0+dfsg-16 to 2.5.2-1): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ seqan2 unsatisfiable Build-Depends(-Arch) on armhf: 
architecture-is-64-bit
∙ ∙ seqan2 unsatisfiable Build-Depends(-Arch) on i386: 
architecture-is-64-bit
∙ ∙ Missing build on armhf
∙ ∙ Missing build on i386
∙ ∙ Missing build on riscv64
∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build
∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
∙ ∙ Autopkgtest for seqan2/2.5.2-1: amd64: Pass, arm64: Pass, ppc64el: 
Pass, s390x: Pass
∙ ∙ Lintian check waiting for test results on armhf, i386, riscv64 - info
∙ ∙ Too young, only 0 of 5 days old
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/s/seqan2.html
∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ 
∙ Waiting for reproducibility test results on arm64 - info ♻
-------------- 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/debian-med-packaging/attachments/20260110/bd43a931/attachment.sig>