On 6 February 2017 at 02:55, Shuduo Sang <shuduo.s...@canonical.com> wrote:
> > > On Fri, Feb 3, 2017 at 4:52 PM, Shuduo Sang <shuduo.s...@canonical.com> > wrote: > >> Hi, >> >> I got following output after run it: >> >> $ go-17-mwhudson.go-17 >> /snap/go-17-mwhudson/2/gowrapper: line 3: /snap/go-17-mwhudson/2/bin/go: >> No such file or directory >> >> My snap version is: >> $ snap version >> snap 2.21 >> snapd 2.21 >> series 16 >> ubuntu 16.04 >> >> Please let me know what mistake I have. >> > > UPDATE: I notice the go binary is referred to library from /snap/core > $ file /snap/go-17-mwhudson/current/bin/go > /snap/go-17-mwhudson/current/bin/go: ELF 64-bit LSB executable, x86-64, > version 1 (SYSV), dynamically linked, interpreter > /snap/core/current/lib/x86_64-linux-gnu/ld-2.23.so, for GNU/Linux 2.6.32, > BuildID[sha1]=3e694c21430e17b6bba99bd1828696a784ffab8a, not stripped > > But I have /snap/ubuntu-core only. > > After refresh ubuntu-core from candidate channel then it transit to > /snap/core now go-17 works well. Thanks zyga's help. > Ah good, glad you got it working. I think this makes sense as a way to distribute Go to people who want to use Go on their machines. I maintain a PPA with backports of new versions of Go to older releases of Ubuntu but it's a bit fiddly and snaps would be better (and also get cross distro coverage). I think to get to the point of it being a good general distribution mechanism, we need: 1) testing (so that's everyone who's downloaded it so far) 2) pick a better snap name, or set of snap names (go-16, go-17, go-18 or go16, go17, go18 or something else?) 3) get it into the stable channel 4) building in Launchpad would surely be nice to get better architecture coverage Have I missed anything? Cheers, mwh
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
