Marked for autoremoval on 14 December due to petsc4py: #1119759high
Version 3.22.2-1 of slepc4py is marked for autoremoval from testing on Sun 14 Dec 2025. It depends (transitively) on petsc4py, affected by #1119759. You should try to prevent the removal by fixing these RC bugs.
vcswatch reports that
this package seems to have a new changelog entry (version
3.24.1-2, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Among the 4 debian patches
available in version 3.24.1-1 of the package,
we noticed the following issues:
4 patches
where the metadata indicates that the patch has not yet been forwarded
upstream. You should either forward the patch upstream or update the
metadata to document its real status.
testing migrations
This package is part of the ongoing testing transition known as auto-petsc4py.
Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release
managers. On the other hand, if your package has problems
preventing it to migrate to testing, please fix them
as soon as possible.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
This package is part of the ongoing testing transition known as auto-slepc.
Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release
managers. On the other hand, if your package has problems
preventing it to migrate to testing, please fix them
as soon as possible.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
This package is part of the ongoing testing transition known as auto-petsc.
Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release
managers. On the other hand, if your package has problems
preventing it to migrate to testing, please fix them
as soon as possible.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/s/slepc4py.png){kind=link}