Marked for autoremoval on 14 December due to petsc4py: #1119759high
Version 2019.2.0~legacy20240219.1c52e83-24 of dolfin 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.
Problems while searching for a new upstream version
high
uscan had problems while searching for a new upstream version:
In debian/watch no matching files for watch source
https://bitbucket.org/fenics-project/dolfin/downloads/
Lintian reports
6 warnings
about this package. You should make the package lintian clean getting rid of them.
debian/patches: 30 patches to forward upstream
low
Among the 30 debian patches
available in version 2019.2.0~legacy20240219.1c52e83-25 of the package,
we noticed the following issues:
30 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-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-scotch.
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.
Migration status for dolfin (2019.2.0~legacy20240219.1c52e83-24 to 2019.2.0~legacy20240219.1c52e83-25): Waiting for test results or another package, or too young (no action required now - check later)
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/dolfin.png){kind=link}