-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't find package github.com/golang-migrate/migrate/v3/database #111
Comments
Have the same issue |
Greetings. My team has started to work on a project recently. Unfortunately, we have faced this issue as well. It really slows us down. Could someone take a look and provide a fix? Thanks in advance. |
Probably related to #103 |
@dhui ,
It won't help. Because there is no v3 package/folder in the master branch of the migrate repo. Thanks for the fast reply. We will wait for updates |
Using a newer version of Go should help as they're module aware |
Problem still exists for |
That's odd since CI is passing... |
In an attempt to find a workaround, I checked out the v3.5.0 branch. However, I cant build or install this, it says: $ cd ~/go/src/github.com/golang-migrate/migrate GOPATH and GOBIN are correctly set and exported. go version go1.10.2 darwin/amd64 In desperation, I also tried downloading the darwin binary, but macos cant execute the resultant file. |
@kostyaVyrodov See how Go modules work: https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher Anyways, a change will be made soon where modules will be removed from v3 and be supported in v4 |
v3.5.3 fixed the problems for me, @dhui . I really appreciate your working on it Dale! |
Describe the Bug
An error during getting github.com/golang-migrate/migrate
Steps to Reproduce
Migrate shouldn't be installed
or
Delete the migrate:
rm -rf $GOPATH/src/github.com/golang-migrate/migrate
go get github.com/golang-migrate/migrate
Expected Behavior
go get installs tge migrate successfully
Go Version
go version go1.10.2 darwin/amd64
Stacktrace
The text was updated successfully, but these errors were encountered: