Hi there, you are no worse situation than you were before. If you are building off of xenial you should be generally ok as long as you do not use CGO as the interpreter is pretty much stable in the world we live today.
Going back to the released deb (2.35 or previous) will lead to the same result, a snap for go that wouldn't work entirely correct on classic.
That said, can I ask you to try the latest snapcraft on the `edge` channel as we have added a work around for golang base parts (it will not be bullet proof).
Alternatively, if you have linker/elf experience, I would invite you to fix this patchelf problem upstream.
Hi there, you are no worse situation than you were before. If you are building off of xenial you should be generally ok as long as you do not use CGO as the interpreter is pretty much stable in the world we live today.
Going back to the released deb (2.35 or previous) will lead to the same result, a snap for go that wouldn't work entirely correct on classic.
That said, can I ask you to try the latest snapcraft on the `edge` channel as we have added a work around for golang base parts (it will not be bullet proof).
Alternatively, if you have linker/elf experience, I would invite you to fix this patchelf problem upstream.
Thanks for the report.