You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go: finding gopkg.in/DATA-DOG/go-sqlmock.v1 v1.3.3
get "gopkg.in/DATA-DOG/go-sqlmock.v1": found meta tag get.metaImport{Prefix:"gopkg.in/DATA-DOG/go-sqlmock.v1", VCS:"git", RepoRoot:"https://gopkg.in/DATA-DOG/go-sqlmock.v1"} at //gopkg.in/DATA-DOG/go-sqlmock.v1?go-get=1
go: finding gopkg.in/DATA-DOG/go-sqlmock.v1 v1.3.3
go get all: cannot find module providing package gopkg.in/DATA-DOG/go-sqlmock.v1
This seemed to break the go get call because my new version never got updated.
I had to run this command to get the latest version of the package
$ go get -v github.com/ardanlabs/conf
go: finding github.com/ardanlabs/conf v1.1.0
go: downloading github.com/ardanlabs/conf v1.1.0
go: extracting github.com/ardanlabs/conf v1.1.0
github.com/ardanlabs/conf
Given this error, I would have liked go get to continue to update the dependencies. This is now trouble because I can't update dependencies without knowing what to update.
I would like to know why this error is occurring on the Datadog packages as well.
The text was updated successfully, but these errors were encountered:
I'm experiencing that go get -u or go get -v is not working without the use of all. If I don't use all I get this error.
$ go get -u
go get .: path /Users/bill/code/go/src/github.com/ardanlabs/service is not a package in module rooted at /Users/bill/code/go/src/github.com/ardanlabs/service
Regardless, this error from the Datadog package is preventing go get to continue its work.
$ go get -u all
go: finding gopkg.in/DATA-DOG/go-sqlmock.v1 v1.3.3
go: finding gopkg.in/DATA-DOG/go-sqlmock.v1 v1.3.3
go get all: cannot find module providing package gopkg.in/DATA-DOG/go-sqlmock.v1
Then the question is, is there different behavior with all using or not using -u or -v?
-u is for update, -v is for verbose output, go get -u works on the current package (which is non-existent at the root of your module), go get -u all works on all dependencies
your other error is from a name mismatch between the import name gopkg.in/DATA-DOG/go-sqlmock.v1 and the module name declared in that module github.com/DATA-DOG/go-sqlmock
Thanks! I found the problem with the datadog issue. I needed a replace to point to a version of go-sqlmock that didn't have a modules file. This is not causing a new issue. I will close this and open a new issue.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Given this project
https://github.com/ardanlabs/service
I wanted to update all of the current dependencies to their current MVS. I updated a package I own and added a new tag. I ran the following command
What did you expect to see?
What did you see instead?
This seemed to break the
go get
call because my new version never got updated.I had to run this command to get the latest version of the package
Given this error, I would have liked
go get
to continue to update the dependencies. This is now trouble because I can't update dependencies without knowing what to update.I would like to know why this error is occurring on the Datadog packages as well.
The text was updated successfully, but these errors were encountered: