Tianon: > Hmm, were you using sbuild? I haven't yet figured out how the best > way to handle what sbuild calls "alternatives" here yet -- it has a > flag to attempt them (--resolve-alternatives), but it's disabled by > default (and thus most of the buildds have it disabled too). The > dependency as listed is correct; we need one of either golang-go or > gccgo-5, and we prefer golang-go.
I was using a manually maintained chroot. I sometimes forget to mount /proc or something like that. What's happening with golang in experimental (https://buildd.debian.org/status/logs.php?pkg=golang&arch=arm64) is similar to what's happening with git-annex in unstable (https://buildd.debian.org/status/logs.php?pkg=git-annex&arch=arm64). You might just have to upload arm64 binaries at some point. > I jumped on an arm64 porterbox to test, and after installing build > deps in my fresh sid schroot (including and especially gccgo-5), the > package did build successfully, including the entire test suite ("ALL > TESTS PASSED"), so I'm not sure what's going on here. :( I'm not sure, but I think I did start with a fresh chroot in that case. It didn't get very far for me at all. It complained about some environment variable not being set. Is it possible that you had a .bashrc or .profile that helped? Thanks for looking into this! Edmund
