Bug#1086890: src:petsc: fails to migrate to testing for too long

[Paul Gevers]

Source: petsc
Version: 3.20.6+dfsg1-3
Severity: serious
Control: close -1 3.21.6+dfsg1-2
Tags: sid trixie
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:petsc has been trying to migrate for 31 
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 
trixie, 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=petsc

Current text from [2]:
Migration status for petsc (3.20.6+dfsg1-3 to 3.21.6+dfsg1-2): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ autopkgtest for petsc/3.21.6+dfsg1-2: amd64: Failed (not a 
regression), armel: Pass, armhf: Pass, i386: Pass
∙ ∙ autopkgtest for petsc4py/3.20.5-4: amd64: Regression or new test ♻ 
(reference ♻), armel: Pass, armhf: Pass, i386: Pass
∙ ∙ autopkgtest for slepc/3.20.2+dfsg1-2: amd64: Regression or new test 
♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass
∙ ∙ autopkgtest for slepc4py/3.20.2-1: amd64: Regression or new test ♻ 
(reference ♻), armel: Pass, armhf: Pass, i386: Pass
∙ ∙ missing build on arm64
∙ ∙ missing build on mips64el
∙ ∙ missing build on ppc64el
∙ ∙ missing build on riscv64
∙ ∙ missing build on s390x
∙ ∙ arch:arm64 not built yet, autopkgtest delayed there
∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there
∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there
∙ ∙ arch:s390x not built yet, autopkgtest delayed there
∙ ∙ Depends: petsc openmpi (not considered)
Additional info:
∙ ∙ Cannot be tested by piuparts (not a blocker) - 
https://piuparts.debian.org/sid/source/p/petsc.html
∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ 
∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ 
Ignoring non-reproducibility on i386 (not a regression) - info ♻ ∙ ∙ 18 
days old (needed 5 days)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20241107/5954c883/attachment.sig>