Re: [go-nuts] Dependency resolution weirdness with Go Modules.

2018-09-27 Thread Josh Harshman
Thanks Paul, I read through that issue you linked and was able to work through the dependency issues. Seems like the issue arises when the dependencies aren't tagging their releases properly. I had to update numerous dependencies to commits past their latest tagged release. On Thursday, Septem

Re: [go-nuts] Dependency resolution weirdness with Go Modules.

2018-09-27 Thread Paul Jolly
Looks related to https://github.com/golang/go/issues/27457. Perhaps a variation of https://github.com/golang/go/issues/27457#issuecomment-419364867 helps in this situation? On Thu, 27 Sep 2018 at 00:51, Josh Harshman wrote: > > Using Go 1.11 and Go Modules to resolve package dependencies for my p

[go-nuts] Dependency resolution weirdness with Go Modules.

2018-09-26 Thread Josh Harshman
Using Go 1.11 and Go Modules to resolve package dependencies for my project. Unfortunately I am running into some vendoring issues and incompatibilities that have me a little stumped. Here is my go.mod file, there are a few packages listed as incompatible etc... go.mod module github.ancestry.co