Hi,

This package is involved in a complicated take-over.
src:golang-github-anacrolix-missinggo-v2 builds binaries formerly built
by src:golang-github-anacrolix-missinggo including an arch:any binary
that was built on all release architectures.
src:golang-github-anacrolix-missinggo-v2 Build-Depends on
bin:golang-github-anacrolix-missinggo-dev.
bin:golang-github-anacrolix-missinggo-dev is an arch:all binary that
Depends on bin:golang-github-anacrolix-missinggo-v2-dev which hasn't
been built yet on riscv64, but is needed to build itself.

src:golang-github-anacrolix-missinggo can't migrate to testing because
its old riscv64 binary hasn't been rebuild yet by the overtaking
package, but as discussed above, it's not going to appear without
interaction.

src:golang-github-anacrolix-missinggo-v2 can't migrate to testing
because it depends on the version of
golang-github-anacrolix-missinggo-dev that can't migrate.

My proposal is that you upload
bin:golang-github-anacrolix-missinggo-v2-dev/riscv64 that you build
manually somehow and then ask the Release Team to binNMU it after that
to get a buildd built binary.

The alternative is to drop riscv64 support by filing an architecture
specific removal bug against the ftp.debian.org pseudo package, but I
consider this an unnecessary drop of support as the current situation is
just a bootstrapping problem which looks solvable with historical
binaries from snapshot.d.o.

Paul