-
Notifications
You must be signed in to change notification settings - Fork 280
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
Cannot go get from a fresh machine #155
Comments
I cannot seem to import this library anymore, it seems to be some dependency to https://github.com/mattn/go-sqlite3 which has a recently closed issue here but I don't think it's fixed properly If i try to I see the following error build github.com/rubenv/sql-migrate/sql-migrate: cannot load github.com/mattn/go-sqlite3: module github.com/mattn/go-sqlite3@latest found (v2.0.0+incompatible), but does not contain package github.com/mattn/go-sqlite3 |
Looks like |
TL/DR: details: This error happens because you try to Since in your case You can fix this by installing sql-migrate in module-aware mode. But, then you will bump into another unrelated error described here mattn/go-sqlite3#755.
|
This sounds like a bug in I don't want to require module support (even though it's great), so there's nothing we can do here. |
It is more like |
To answer my own question, yes GO111MODULE=on is necessary |
Hi, I am sorry for causing this bug. It looks like this project depends on github.com/mitchellh/cli which depends on github.com/posener/complete. I don't like the v2 directory solution as versioning solution in Go. The v1 is still available through git branch or git tags, also proposed by the strategies in the Go blog. About solutions: |
No worries, that happens! |
@posener If adding /v2/ subdir feels ugly, maybe you can create a new v2 branch (and make it github default)? |
@drscre good idea! |
I'm having troubles there, since the CLI library should also be compatible with older Go versions. |
This needs more work, just tested it on a fresh linux box and still not building. |
Same error?
…On Tue, Nov 19, 2019, 15:11 Mauricio Leyzaola ***@***.***> wrote:
This needs more work, just tested it on a fresh linux box and still not
building. I know you like to keep things simple.
As a temporary workaround I forked this repo, grabbed the dependencies via dep
ensure and push them all to my forked repo.
That compiles well but has the obvious advantages.
Just in case someone else is struggling with this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#155?email_source=notifications&email_token=AAHAN7UJNCCENXNOBCWDQP3QUPQWVA5CNFSM4JON4BSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEOEJEA#issuecomment-555500688>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHAN7RRNJIRLYEJHSZBS6TQUPQWVANCNFSM4JON4BSA>
.
|
@posener Yeah
|
FYI we are also seeing the indirect dependency through |
@posener it turns out that |
rubenv#155 posener/complete#107 Posener introduced breaking changes to the `complete` repository, `sql-migrate` depends on that repository and can therefore not be built anymore. Intermediate solution is to fork repo and push dependencies.
I updated the default branch. Looking for a solution if anyone has one.
…On Wed, Nov 20, 2019, 10:09 Ivan Skriabin ***@***.***> wrote:
@posener <https://github.com/posener> it turns out that go get uses
default branch, not master :/. You should change default branch to master.
Sorry for misleading you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#155?email_source=notifications&email_token=AAHAN7V2UHPI6H4QK3KRRPLQUTWFHA5CNFSM4JON4BSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEERDBQQ#issuecomment-555888834>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHAN7WXABHU755VTZV4FWTQUTWFHANCNFSM4JON4BSA>
.
|
I think you can close this issue. Thanks for the help! |
This is a machine which has no golang code on it, like a fresh install
OUTPUT
ENVIRONMENT
The text was updated successfully, but these errors were encountered: