We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:
basix | 0.0.1~git20210305.fe8fada-1 | source
basix | 0.0.1~git20210409.b980196-2 | source
basix-doc | 0.0.1~git20210305.fe8fada-1 | all
dolfinx | 2019.2.0~git20210304.146860e-2 | source
dolfinx | 2019.2.0~git20210410.b421249-2 | source
dolfinx-doc | 2019.2.0~git20210304.146860e-2 | all
dolfinx-doc | 2019.2.0~git20210410.b421249-2 | all
libbasix-dev | 0.0.1~git20210305.fe8fada-1 | mipsel
libbasix0 | 0.0.1~git20210305.fe8fada-1 | mipsel
libdolfinx-complex-dev | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel
libdolfinx-complex-dev | 2019.2.0~git20210410.b421249-2 | armhf
libdolfinx-complex2019.2 | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel, ppc64el, s390x
libdolfinx-complex2019.2 | 2019.2.0~git20210410.b421249-2 | amd64, arm64, armhf, mips64el
libdolfinx-dev | 2019.2.0~git20210304.146860e-2 | all
libdolfinx-dev | 2019.2.0~git20210410.b421249-2 | all
libdolfinx-real-dev | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel
libdolfinx-real-dev | 2019.2.0~git20210410.b421249-2 | armhf
libdolfinx-real2019.2 | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel, ppc64el, s390x
libdolfinx-real2019.2 | 2019.2.0~git20210410.b421249-2 | amd64, arm64, armhf, mips64el
python3-basix | 0.0.1~git20210305.fe8fada-1 | mipsel
python3-dolfinx | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel
python3-dolfinx | 2019.2.0~git20210410.b421249-2 | armhf
python3-dolfinx-complex | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel
python3-dolfinx-complex | 2019.2.0~git20210410.b421249-2 | armhf
python3-dolfinx-real | 2019.2.0~git20210304.146860e-2 | armel, i386, mipsel
python3-dolfinx-real | 2019.2.0~git20210410.b421249-2 | armhf
------------------- Reason -------------------
RoQA; renamed to src:fenics-{basix,dolfinx}
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System. Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1004609@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/1004609
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
