Missing "package" about go-package-store

[dmitshur]

Hi, please try the go get -u github.com/shurcooL/Go-Package-Store command again, it should work.

I think it's a bug in go get -u where if package import paths change at the same time as packages are removed, it reports a problem incorrectly. I'll try to get it reported and fixed if so.

On a stylistic note, "gist7519227" is a rather meaningless name for a package, and that huge list of external gist "packages" creates exactly the brittleness seen here.

I agree about the name being poor, and I've been working on improving that, which is precisely why this happened. So it would actually be fine if I hadn't done anything. But I think it's worth improving the package names. You can see shurcooL/go@a9d7bb9 where I refactored and removed many of those low quality packages. Go Package Store still works after the refactor, so this is just a minor go get -u issue.

Let me know if running go get -u a second time does not fix it.

[dmitshur]

Also, the Travis build is passing, suggesting that it should work fine.

[andrewslotin]

Hi!

I just tried to update my Go-Package-Store and got the same issue as @sethwklein, plus a similar error about github.com/shurcooL/go/gists/gist5286084 and I can confirm that retry helps. I assume that the problem is in $GOPATH/pkg/.../github.com/shurcooL/Go-Package-Store/presenter.a that left from a previous installation.

[sethwklein]

I retried now and it worked.

[dmitshur]

Thanks for confirming.

I will try to make a smaller reproducible case and submit/find a bug report for this go get issue and try to get it fixed. I plan to do more refactoring and package renaming, and I don't want it to keep happening for users.

[dmitshur]

By the way, @sethwklein, is there a reason you didn't use Go Package Store to update Go Package Store?

[sethwklein]

@shurcooL yes, I encountered the error while attempting to install Go Package Store.

[dmitshur]

I will try to make a smaller reproducible case and submit/find a bug report for this go get issue and try to get it fixed. I plan to do more refactoring and package renaming, and I don't want it to keep happening for users.

I've done so in golang/go#9224.