Package: golang-any Severity: normal X-Debbugs-Cc: z...@debian.org While reply https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031330#22 I realize we have similar problem when building Go programs in experimental and backports. The aspcud resolver for unknown reason that prefers gccgo-go on arch where golang-go is available. That causes unexpected build failures, especially annoying for backports.
While it's good to keep packages buildable with gccgo, the reality is only golang-go is tested on sid. So we can't know the build failures in advance. So we should remove the alternative Depends in golang-any, to have a determinate result. I think we previously use "golang-go | gccgo-go" because it's easies to write debian/control file. Can we have different Depends for different arch? Can we reduce the duplication of arch list with golang-go?
