On Thu, Dec 10, 2020 at 11:42 PM Reinhard Tartler <[email protected]> wrote: > > > > On Fri, Oct 30, 2020 at 5:31 AM Shengjing Zhu <[email protected]> wrote: >> >> >> > I suspect this could be related to version of golang, in >> > unstable/testing it is 1.15 so we may need the newer golang version. >> > Can someone confirm if this is indeed the case? If yes, do we plan to >> > backport golang 1.15? I can also help with backporting. >> > >> >> I think it has happened before? The aptitude resolver has a problem in >> -backports to pick up gccgo rather than golang-go. >> gccgo in buster only implements go1.10 > > > What seems to work in my testing on backporting golang-github-moby-sys is to > declare a Build-Conflicts on gccgo to force it to use go1.14. >
Not sure how to solve this. Changing golang-any to golang-go also works. Both *-backport and experimental have problems that gccgo-go is chosen instead of golang-go. And it's not clear whether it's a bug or feature, and which package to complain about... -- Shengjing Zhu
