Your message dated Mon, 19 Oct 2026 21:40:38 +0200
with message-id <E1xItDq-000000008s8-1Coh@gelly>
and subject line Re: golang-github-anacrolix-missinggo-v2: Build dependency
cycle and binary takeover preventing migration [riscv64]
has caused the Debian Bug report #1150265,
regarding golang-github-anacrolix-missinggo-v2: Build dependency cycle and
binary takeover preventing migration [riscv64]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1150265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150265
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: golang-github-anacrolix-missinggo-v2
Version: 2.1.0-11
Severity: normal
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
--- End Message ---
--- Begin Message ---
fixed 1150265 2.1.0-12
thanks
golang-github-anacrolix-missinggo-bin-static is migrated to testing
(including riscv64) so closing this bug now.
Drew
--- End Message ---
