Содержание
- cmd/go: «error loading module requirements» from ‘go mod download’ #29213
- Comments
- What version of Go are you using ( go version )?
- What operating system and processor architecture are you using ( go env )?
- What did you do?
- What did you expect to see?
- What did you see instead?
- Go mod error loading requirements and unknown revisions #39475
- Comments
- What version of Go are you using ( go version )?
- Does this issue reproduce with the latest release?
- What operating system and processor architecture are you using ( go env )?
- What did you do?
- What did you expect to see?
- What did you see instead?
- replace directive in parent causes, error loading module requirements #29376
- Comments
- What version of Go are you using ( go version )?
- Does this issue reproduce with the latest release?
- What operating system and processor architecture are you using ( go env )?
- What did you do?
- What did you expect to see?
- What did you see instead?
- Footer
- go get: error loading module requirements #41
- Comments
- Footer
- replace directive in parent causes, error loading module requirements #29376
- Comments
- What version of Go are you using ( go version )?
- Does this issue reproduce with the latest release?
- What operating system and processor architecture are you using ( go env )?
- What did you do?
- What did you expect to see?
- What did you see instead?
- Footer
cmd/go: «error loading module requirements» from ‘go mod download’ #29213
What version of Go are you using ( go version )?
What operating system and processor architecture are you using ( go env )?
What did you do?
Create an image docker
What did you expect to see?
What did you see instead?
Step 6/10 : RUN go mod download
—> Running in 414efa3e565e
go: finding github.com/gorilla/mux v1.6.2
go: github.com/gorilla/mux@v1.6.2: unknown revision v1.6.2
go: error loading module requirements
The command ‘/bin/sh -c go mod download’ returned a non-zero code: 1
The text was updated successfully, but these errors were encountered:
Please mention the exact steps so that we can reproduce this at our end.
What is the Dockerfile ? What is the repo ? Is there a go.mod ?
This is what I get —
Timed out in state WaitingForInfo. Closing.
(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)
Facing the same error
» go clean -modcache
go: finding github.com/pkg/errors v0.8.1
go: finding github.com/go-sql-driver/mysql v1.4.1
go: finding github.com/go-goracle/goracle v2.1.14+incompatible
go: github.com/go-goracle/goracle@v2.1.14+incompatible: unknown revision v2.1.14
go: github.com/go-sql-driver/mysql@v1.4.1: unknown revision v1.4.1
go: github.com/pkg/errors@v0.8.1: unknown revision v0.8.1
go: finding gopkg.in/goracle.v2 v2.13.1
go: gopkg.in/goracle.v2@v2.13.1: unknown revision v2.13.1
go: error loading module requirement»
I am also encountering this problem.
Some more information would be awesome like:
This message is just not useful
Yup I’m also getting this and it’s unclear why.
Источник
Go mod error loading requirements and unknown revisions #39475
What version of Go are you using ( go version )?
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using ( go env )?
What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
Per the Go project’s release policy, go 1.12.7 has been unsupported since 2020-02-25 (when go 1.14 was released), and we have added workarounds for a number of git client bugs since 1.12.7.
Please try go1.14.4 (the current release) and let us know if this issue is still reproducible, and if so with which git client version.
yes I installed gvm yesterday shortly after creating this ticket,
and then go mod tidy -v succeed.
And I ran those commands from my (zsh) terminal outside vscode.
Then I had problem when doing things from vscode terminal / tools (run go mod tidy -v , automated coverage test on save, problems tab) and when I check go version , go env from vscode terminal, it still shows 1.12.7 and old GOPATH (as opposed to new one by gvm)
What is the solution for those so that my vscode is aligned with the gvm ?
Then I also found gvm extension on vscode, I installed it, set the go to 1.13 like I did before, and finally the go version on vscode matches with the terminal outside vscode.
Is «downloading gvm extension on vscode» really is the proper solution I asked earlier?
I have no idea about gvm or how it works. Generally extensions like vscode should use whichever go command is first in $PATH , so you might check what PATH you’re running vscode with. (If you’re starting vscode using a GUI, typically that environment is set in your .profile script rather than .zshrc , and you’ll need to log out and back in to pick up changes.)
Источник
replace directive in parent causes, error loading module requirements #29376
What version of Go are you using ( go version )?
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using ( go env )?
What did you do?
create this main.go file;
and ran;
go1.12beta1 run main.go
What did you expect to see?
success or a helpful error message
What did you see instead?
The text was updated successfully, but these errors were encountered:
The module github.com/perlin-network/life has a replace directive in it’s go.mod file:
https://github.com/perlin-network/life/blob/28a99a6d79ec86732bd0eca66fe45c88f7f29bbc/go.mod#L3
that directive is ignored leading to this failure.
unfortunately, the error message doesn’t point out that it is as a result of an ignored replace directive in the parent module( github.com/perlin-network/life ) and thus making it hard to diagnose what is going on.
go1.12beta1 run main.go
thee parent module github.com/komuw/meli has replacement; https://github.com/komuw/meli/blob/master/go.mod#L47-L53 that get ignored
@gopherbot, please add label modules
The error message here describes exactly the problem: go: github.com/go-interpreter/wagon@v0.0.0: unknown revision v0.0.0 . There is, indeed, no such version tagged in the repository, and (by design) replacements have no effect unless the module containing the replace directive is the main module.
We should not point out that it is the result of an ignored replace directive, because replace directives from other modules are always ignored. The problem is the invalid version in the require directive, and it would exist even without the corresponding replace .
Arguably go mod tidy within github.com/perlin-network/life should either choose a valid version or report an error; it does not today, and that’s #29182.
The situation in github.com/komuw/meli is worse, because the module owner is specifying incompatible versions: the require section declares a dependency on github.com/docker/distribution v2.6.2+incompatible , but the replace section selects what appears to be a semantically older version ( v2.6.0-rc.1.0.20180820212402-02bf4a2887a4+incompatible ).
If that commit really is newer than v2.6.2 , then it should have a newer pseudo-version. In fact, that commit seems to have been tagged v2.7.0 , which gives you an upgrade path to fix the problem. The solution with docker/docker is similar: explicitly go get the master version rather than the latest semantic tag.
The problems in these cases are semantic defects in the declared requirements, not directly due to replace directives. We should do more to prevent those semantic defects, rather than attributing them to only-semi-related features that are working as documented.
I think the thing that will fix the semantic defects is #29182, or perhaps #26420 (comment). Closing as a duplicate of those.
© 2023 GitHub, Inc.
You can’t perform that action at this time.
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.
Источник
go get: error loading module requirements #41
I am on latest release of Go And Buffalo
Follwing is the output of installation
Is this due to some outdated dependencies.
Following is the output :
go get -u github.com/gobuffalo/buffalo-auth
go: finding github.com/gobuffalo/attrs latest
go: finding github.com/serenize/snaker latest
go: finding golang.org/x/crypto latest
go: finding github.com/gobuffalo/meta latest
go: finding golang.org/x/sync latest
go: finding github.com/gobuffalo/logger latest
go: finding golang.org/x/tools latest
go: finding github.com/gobuffalo/licenser latest
go: finding github.com/markbates/oncer latest
go: finding github.com/sourcegraph/syntaxhighlight latest
go: finding github.com/ugorji/go/codec latest
go: finding golang.org/x/sys latest
go: finding github.com/armon/consul-api latest
go: finding golang.org/x/net latest
go: finding github.com/gobuffalo/gitgen latest
go: finding github.com/sourcegraph/annotate latest
go: finding github.com/gobuffalo/helpers latest
go: finding github.com/gobuffalo/syncx latest
go: finding github.com/google/pprof latest
go: finding gopkg.in/tomb.v1 latest
go: finding gopkg.in/check.v1 latest
go: finding golang.org/x/lint latest
go: finding github.com/shurcooL/highlight_diff latest
go: finding google.golang.org/genproto latest
go: finding github.com/prometheus/procfs latest
go: finding github.com/shurcooL/go latest
go: finding github.com/golang/glog latest
go: finding golang.org/x/oauth2 latest
go: finding golang.org/x/build latest
go: finding github.com/anmitsu/go-shlex latest
go: finding github.com/shurcooL/octicon latest
go: finding github.com/jellevandenhooff/dkim latest
go: finding honnef.co/go/tools latest
go: finding github.com/googleapis/gax-go v2.0.2+incompatible
go: finding github.com/shurcooL/home latest
go: finding github.com/neelance/astrewrite latest
go: finding github.com/tarm/serial latest
go: finding github.com/shurcooL/go-goon latest
go: finding github.com/shurcooL/github_flavored_markdown latest
go: finding github.com/shurcooL/events latest
go: finding dmitri.shuralyov.com/html/belt latest
go: finding dmitri.shuralyov.com/service/change latest
go: finding github.com/shurcooL/notifications latest
go: finding dmitri.shuralyov.com/state latest
go: finding github.com/shurcooL/users latest
go: finding github.com/bradfitz/go-smtpd latest
go: finding github.com/gregjones/httpcache latest
go: finding golang.org/x/time latest
go: finding github.com/shurcooL/highlight_go latest
go: finding github.com/shurcooL/httpgzip latest
go: finding github.com/shurcooL/gofontwoff latest
go: finding github.com/shurcooL/httpfs latest
go: finding github.com/coreos/go-systemd latest
go: finding github.com/shurcooL/httperror latest
go: finding github.com/golang/lint latest
go: finding github.com/flynn/go-shlex latest
go: github.com/golang/lint@v0.0.0-20190409202823-959b441ac422: parsing go.mod: unexpected module path «golang.org/x/lint»
go: sourcegraph.com/sourcegraph/go-diff@v0.5.1: parsing go.mod: unexpected module path «github.com/sourcegraph/go-diff»
go: finding golang.org/x/tools v0.0.0-20190114222345-bf090417da8b
go: finding github.com/shurcooL/issues latest
go: finding github.com/shurcooL/reactions latest
go: finding github.com/shurcooL/gopherjslib latest
go: finding github.com/shurcooL/issuesapp latest
go: finding golang.org/x/perf latest
go get: error loading module requirements
The text was updated successfully, but these errors were encountered:
Execute go get -u github.com/gobuffalo/buffalo-auth outside project folder.
If it works please close this issue.
I get the same issue, and I run go get command at $HOME folder. Please advise.
zwang-mac:
zwang$ go get gitlab.vm.domaintools.net/backend/gatheringsystem/remington go: finding gitlab.vm.domaintools.net/backend/gatheringsystem/remington latest go: finding github.com/beorn7/perks v1.0.1 go: finding github.com/googleapis/gax-go/v2 v2.0.5 go: finding golang.org/x/sys v0.0.0-20190507160741-ecd444e8653b go: finding golang.org/x/sys v0.0.0-20190801041406-cbf593c0f2f3 go: finding golang.org/x/sys v0.0.0-20190509141414-a5b02f93d862 go: finding golang.org/x/net v0.0.0-20190503192946-f4e77d36d62c go: finding golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 go: finding golang.org/x/tools v0.0.0-20190506145303-2d16b83fe98c go: finding google.golang.org/appengine v1.5.0 go: finding golang.org/x/lint v0.0.0-20190409202823-959b441ac422 go: finding golang.org/x/net v0.0.0-20190108225652-1e06a53dbb7e go: finding github.com/hashicorp/golang-lru v0.5.1 go: finding github.com/knq/sysutil v0.0.0-20181215143952-f05b59f0f307 go: finding github.com/gobwas/httphead v0.0.0-20180130184737-2c6c146eadee go: finding github.com/golang/mock v1.3.1 go: finding go.opencensus.io v0.21.0 go: finding honnef.co/go/tools v0.0.0-20190418001031-e561f6794a2a go: finding cloud.google.com/go v0.34.0 go: finding google.golang.org/api v0.8.0 go: finding rsc.io/binaryregexp v0.2.0 go: finding github.com/json-iterator/go v1.1.7 go: finding gitlab.vm.domaintools.net/backend/gatheringsystem/gatherc/v3 v3.3.2 go: finding cloud.google.com/go v0.38.0 go: gitlab.vm.domaintools.net/backend/gatheringsystem/gatherc/v3@v3.3.2: unknown revision gatherc/v3.3.2 go: finding github.com/gobwas/pool v0.2.0 go: finding github.com/gobwas/ws v1.0.0 go: finding google.golang.org/genproto v0.0.0-20190801165951-fa694d86fc64 go: finding go.opencensus.io v0.22.0 go: finding golang.org/x/tools v0.0.0-20190628153133-6cdbf07be9d0 go: finding github.com/google/pprof v0.0.0-20190515194954-54271f7e092f go: finding cloud.google.com/go/datastore v1.0.0 go: finding github.com/mailru/easyjson v0.0.0-20180823135443-60711f1a8329 go: finding github.com/jstemmer/go-junit-report v0.0.0-20190106144839-af01ea7f8024 go: finding google.golang.org/genproto v0.0.0-20190502173448-54afdca5d873 go: finding google.golang.org/grpc v1.21.1 go: finding google.golang.org/grpc v1.20.1 go: finding github.com/mailru/easyjson v0.0.0-20190403194419-1ea4449da983 go: finding github.com/google/martian v2.1.0+incompatible go: finding golang.org/x/exp v0.0.0-20190510132918-efd6b22b2522 go: error loading module requirements
outdated. closing, but please feel free to reopen the issue if someone need help for the same issue.
© 2023 GitHub, Inc.
You can’t perform that action at this time.
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.
Источник
replace directive in parent causes, error loading module requirements #29376
What version of Go are you using ( go version )?
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using ( go env )?
What did you do?
create this main.go file;
and ran;
go1.12beta1 run main.go
What did you expect to see?
success or a helpful error message
What did you see instead?
The text was updated successfully, but these errors were encountered:
The module github.com/perlin-network/life has a replace directive in it’s go.mod file:
https://github.com/perlin-network/life/blob/28a99a6d79ec86732bd0eca66fe45c88f7f29bbc/go.mod#L3
that directive is ignored leading to this failure.
unfortunately, the error message doesn’t point out that it is as a result of an ignored replace directive in the parent module( github.com/perlin-network/life ) and thus making it hard to diagnose what is going on.
go1.12beta1 run main.go
thee parent module github.com/komuw/meli has replacement; https://github.com/komuw/meli/blob/master/go.mod#L47-L53 that get ignored
@gopherbot, please add label modules
The error message here describes exactly the problem: go: github.com/go-interpreter/wagon@v0.0.0: unknown revision v0.0.0 . There is, indeed, no such version tagged in the repository, and (by design) replacements have no effect unless the module containing the replace directive is the main module.
We should not point out that it is the result of an ignored replace directive, because replace directives from other modules are always ignored. The problem is the invalid version in the require directive, and it would exist even without the corresponding replace .
Arguably go mod tidy within github.com/perlin-network/life should either choose a valid version or report an error; it does not today, and that’s #29182.
The situation in github.com/komuw/meli is worse, because the module owner is specifying incompatible versions: the require section declares a dependency on github.com/docker/distribution v2.6.2+incompatible , but the replace section selects what appears to be a semantically older version ( v2.6.0-rc.1.0.20180820212402-02bf4a2887a4+incompatible ).
If that commit really is newer than v2.6.2 , then it should have a newer pseudo-version. In fact, that commit seems to have been tagged v2.7.0 , which gives you an upgrade path to fix the problem. The solution with docker/docker is similar: explicitly go get the master version rather than the latest semantic tag.
The problems in these cases are semantic defects in the declared requirements, not directly due to replace directives. We should do more to prevent those semantic defects, rather than attributing them to only-semi-related features that are working as documented.
I think the thing that will fix the semantic defects is #29182, or perhaps #26420 (comment). Closing as a duplicate of those.
© 2023 GitHub, Inc.
You can’t perform that action at this time.
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.
Источник
I want to update my package but when i run -v command to get latest updates the command line hit an err
go get -v ./...
what happens?
> go: finding github.com/aws/aws-sdk-go v1.17.11 go: finding
> github.com/aws/aws-sdk-go v1.17.7 go: finding
> github.com/aws/aws-sdk-go v1.16.32 go:
> github.com/aws/aws-sdk-go@v1.17.7: git -c protocol.version=0 fetch
> --unshallow -f https://github.com/aws/aws-sdk-go refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in
> /Users/fly/go/pkg/mod/cache/vcs/cb1953cbdfd14fc2ffce4dfd06487e8d5a0c96da00d00bdef65874ff644eaa26:
> exit status 128: warning: redirecting to
> https://github.com/aws/aws-sdk-go/ fatal: Unable to create
> '/Users/fly/go/pkg/mod/cache/vcs/cb1953cbdfd14fc2ffce4dfd06487e8d5a0c96da00d00bdef65874ff644eaa26/shallow.lock':
> File exists.
>
> Another git process seems to be running in this repository, e.g. an
> editor opened by 'git commit'. Please make sure all processes are
> terminated then try again. If it still fails, a git process may have
> crashed in this repository earlier: remove the file manually to
> continue. go: github.com/aws/aws-sdk-go@v1.16.32: unknown revision
> v1.16.32 go: github.com/aws/aws-sdk-go@v1.17.11: unknown revision
> v1.17.11 go: error loading module requirements
Jonathan Hall
72.2k15 gold badges140 silver badges183 bronze badges
asked Mar 17, 2019 at 9:18
The error message is pretty clear here:
Another git process seems to be running in this repository, e.g. an
editor opened by ‘git commit’. Please make sure all processes are
terminated then try again.
When you run go get
the git
command is used to load everything. So there is another process using git.
Just end the other git command and it will work.
answered Mar 17, 2019 at 9:55
apxpapxp
4,8304 gold badges21 silver badges42 bronze badges
2
cmd/go: «error loading module requirements» from ‘go mod download’ #29213
Comments
TPTan96 commented Dec 13, 2018
What version of Go are you using ( go version )?
What operating system and processor architecture are you using ( go env )?
What did you do?
Create an image docker
What did you expect to see?
What did you see instead?
Step 6/10 : RUN go mod download
—> Running in 414efa3e565e
go: finding github.com/gorilla/mux v1.6.2
go: github.com/gorilla/mux@v1.6.2: unknown revision v1.6.2
go: error loading module requirements
The command ‘/bin/sh -c go mod download’ returned a non-zero code: 1
The text was updated successfully, but these errors were encountered:
agnivade commented Dec 13, 2018
Please mention the exact steps so that we can reproduce this at our end.
What is the Dockerfile ? What is the repo ? Is there a go.mod ?
This is what I get —
gopherbot commented Jan 14, 2019
Timed out in state WaitingForInfo. Closing.
(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)
varuntechie commented May 6, 2019
Facing the same error
» go clean -modcache
go: finding github.com/pkg/errors v0.8.1
go: finding github.com/go-sql-driver/mysql v1.4.1
go: finding github.com/go-goracle/goracle v2.1.14+incompatible
go: github.com/go-goracle/goracle@v2.1.14+incompatible: unknown revision v2.1.14
go: github.com/go-sql-driver/mysql@v1.4.1: unknown revision v1.4.1
go: github.com/pkg/errors@v0.8.1: unknown revision v0.8.1
go: finding gopkg.in/goracle.v2 v2.13.1
go: gopkg.in/goracle.v2@v2.13.1: unknown revision v2.13.1
go: error loading module requirement»
joshmsamuels commented Jun 24, 2019
I am also encountering this problem.
alwinmarkcf commented Jul 18, 2019
Some more information would be awesome like:
This message is just not useful
Integralist commented Sep 19, 2019
Yup I’m also getting this and it’s unclear why.
Источник
cmd/go: difficulty resolving ‘error loading module requirements’ with kubernetes #32864
Comments
medyagh commented Jul 1, 2019
What version of Go are you using ( go version )?
Does this issue reproduce with the latest release?
Yes, I am using latest.
What operating system and processor architecture are you using ( go env )?
What did you do?
in minikube go.mod I bumped k8s.io/kubernetes v1.11.3 to k8s.io/kubernetes v1.15.0
and I ran go mod tidy -v
What did you expect to see?
I expected it update my dependency or tell me what is blocking it form doing so.
What did you see instead?
go: error loading module requirements
The failing go.mod
The text was updated successfully, but these errors were encountered:
AlexRouSg commented Jul 1, 2019 •
Specifically this comment #32776 (comment)
k8s.io/kubernetes is not primarily intended to be consumed as a module. Only the published subcomponents are (and go get works properly with those).
If you want to consume k8s.io/kubernetes as a module, you’d probably need to add require directives for matching versions of all of the subcomponents, rather than using go get
medyagh commented Jul 1, 2019
Thanks for the response @AlexRouSg . I understand that I would need to add all the indirect modules myself but the error message on go mod tidy was not even remotely helping me. Or others that might have same issue.
I was hoping by adding -v I could get some more details. Is there any way go mod could provide more context or more helpful error message?
medyagh commented Jul 1, 2019
Plus I had the same issue when I was trying to use the sub package. ( Either client-go or kubectl)
I was able to solve my problem with go dep . I was hoping go mod could catch up with go dep
AlexRouSg commented Jul 1, 2019
The error message is actually:
The unknown revision v0.0.0 parts are the hints on what’s wrong. Do you have any suggestions on what would be a better message?
medyagh commented Jul 1, 2019 •
The unknown revision v0.0.0 parts are the hints on what’s wrong. Do you have any suggestions on what would be a better message?
in my go.mod file I have the commit ID for them for example ( 1f13a808da65 ) for k8s.io/client-go v0.0.0-20180806134042-1f13a808da65 , so I don’t undrestand why go mod thinks it has not been given a revision ?
and more importantly, if I revert back the k8s.io/kubernetes v1.15.0 version from 1.15.0 to 1.11.3 , it will not be yelling about unknown revision for any of them (including client-go) and worked fine. so it is inconsistent error and it failed to undrestand that the source of the problem is k8s.io/kubernetes v1.15.0 everything else is fine.
so I don’t think it is unknown revision since i have given the commit id to it.
AlexRouSg commented Jul 1, 2019 •
1.11.3 was before they added modules support so things just work the old way.
Источник
Go mod error loading requirements and unknown revisions #39475
Comments
leguminosa commented Jun 9, 2020
What version of Go are you using ( go version )?
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using ( go env )?
What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
bcmills commented Jun 10, 2020 •
Per the Go project’s release policy, go 1.12.7 has been unsupported since 2020-02-25 (when go 1.14 was released), and we have added workarounds for a number of git client bugs since 1.12.7.
Please try go1.14.4 (the current release) and let us know if this issue is still reproducible, and if so with which git client version.
leguminosa commented Jun 11, 2020 •
yes I installed gvm yesterday shortly after creating this ticket,
and then go mod tidy -v succeed.
And I ran those commands from my (zsh) terminal outside vscode.
Then I had problem when doing things from vscode terminal / tools (run go mod tidy -v , automated coverage test on save, problems tab) and when I check go version , go env from vscode terminal, it still shows 1.12.7 and old GOPATH (as opposed to new one by gvm)
What is the solution for those so that my vscode is aligned with the gvm ?
Then I also found gvm extension on vscode, I installed it, set the go to 1.13 like I did before, and finally the go version on vscode matches with the terminal outside vscode.
Is «downloading gvm extension on vscode» really is the proper solution I asked earlier?
bcmills commented Jun 11, 2020
I have no idea about gvm or how it works. Generally extensions like vscode should use whichever go command is first in $PATH , so you might check what PATH you’re running vscode with. (If you’re starting vscode using a GUI, typically that environment is set in your .profile script rather than .zshrc , and you’ll need to log out and back in to pick up changes.)
Источник
replace directive in parent causes, error loading module requirements #29376
Comments
komuw commented Dec 21, 2018
What version of Go are you using ( go version )?
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using ( go env )?
What did you do?
create this main.go file;
and ran;
go1.12beta1 run main.go
What did you expect to see?
success or a helpful error message
What did you see instead?
The text was updated successfully, but these errors were encountered:
komuw commented Dec 21, 2018
The module github.com/perlin-network/life has a replace directive in it’s go.mod file:
https://github.com/perlin-network/life/blob/28a99a6d79ec86732bd0eca66fe45c88f7f29bbc/go.mod#L3
that directive is ignored leading to this failure.
unfortunately, the error message doesn’t point out that it is as a result of an ignored replace directive in the parent module( github.com/perlin-network/life ) and thus making it hard to diagnose what is going on.
komuw commented Dec 21, 2018
go1.12beta1 run main.go
thee parent module github.com/komuw/meli has replacement; https://github.com/komuw/meli/blob/master/go.mod#L47-L53 that get ignored
komuw commented Dec 21, 2018
@gopherbot, please add label modules
bcmills commented Dec 21, 2018
The error message here describes exactly the problem: go: github.com/go-interpreter/wagon@v0.0.0: unknown revision v0.0.0 . There is, indeed, no such version tagged in the repository, and (by design) replacements have no effect unless the module containing the replace directive is the main module.
We should not point out that it is the result of an ignored replace directive, because replace directives from other modules are always ignored. The problem is the invalid version in the require directive, and it would exist even without the corresponding replace .
Arguably go mod tidy within github.com/perlin-network/life should either choose a valid version or report an error; it does not today, and that’s #29182.
bcmills commented Dec 21, 2018
The situation in github.com/komuw/meli is worse, because the module owner is specifying incompatible versions: the require section declares a dependency on github.com/docker/distribution v2.6.2+incompatible , but the replace section selects what appears to be a semantically older version ( v2.6.0-rc.1.0.20180820212402-02bf4a2887a4+incompatible ).
If that commit really is newer than v2.6.2 , then it should have a newer pseudo-version. In fact, that commit seems to have been tagged v2.7.0 , which gives you an upgrade path to fix the problem. The solution with docker/docker is similar: explicitly go get the master version rather than the latest semantic tag.
bcmills commented Dec 21, 2018 •
The problems in these cases are semantic defects in the declared requirements, not directly due to replace directives. We should do more to prevent those semantic defects, rather than attributing them to only-semi-related features that are working as documented.
bcmills commented Dec 21, 2018
I think the thing that will fix the semantic defects is #29182, or perhaps #26420 (comment). Closing as a duplicate of those.
Footer
© 2023 GitHub, Inc.
You can’t perform that action at this time.
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.
Источник
go get: error loading module requirements #41
Comments
Niklao commented Apr 28, 2019
I am on latest release of Go And Buffalo
Follwing is the output of installation
Is this due to some outdated dependencies.
Following is the output :
go get -u github.com/gobuffalo/buffalo-auth
go: finding github.com/gobuffalo/attrs latest
go: finding github.com/serenize/snaker latest
go: finding golang.org/x/crypto latest
go: finding github.com/gobuffalo/meta latest
go: finding golang.org/x/sync latest
go: finding github.com/gobuffalo/logger latest
go: finding golang.org/x/tools latest
go: finding github.com/gobuffalo/licenser latest
go: finding github.com/markbates/oncer latest
go: finding github.com/sourcegraph/syntaxhighlight latest
go: finding github.com/ugorji/go/codec latest
go: finding golang.org/x/sys latest
go: finding github.com/armon/consul-api latest
go: finding golang.org/x/net latest
go: finding github.com/gobuffalo/gitgen latest
go: finding github.com/sourcegraph/annotate latest
go: finding github.com/gobuffalo/helpers latest
go: finding github.com/gobuffalo/syncx latest
go: finding github.com/google/pprof latest
go: finding gopkg.in/tomb.v1 latest
go: finding gopkg.in/check.v1 latest
go: finding golang.org/x/lint latest
go: finding github.com/shurcooL/highlight_diff latest
go: finding google.golang.org/genproto latest
go: finding github.com/prometheus/procfs latest
go: finding github.com/shurcooL/go latest
go: finding github.com/golang/glog latest
go: finding golang.org/x/oauth2 latest
go: finding golang.org/x/build latest
go: finding github.com/anmitsu/go-shlex latest
go: finding github.com/shurcooL/octicon latest
go: finding github.com/jellevandenhooff/dkim latest
go: finding honnef.co/go/tools latest
go: finding github.com/googleapis/gax-go v2.0.2+incompatible
go: finding github.com/shurcooL/home latest
go: finding github.com/neelance/astrewrite latest
go: finding github.com/tarm/serial latest
go: finding github.com/shurcooL/go-goon latest
go: finding github.com/shurcooL/github_flavored_markdown latest
go: finding github.com/shurcooL/events latest
go: finding dmitri.shuralyov.com/html/belt latest
go: finding dmitri.shuralyov.com/service/change latest
go: finding github.com/shurcooL/notifications latest
go: finding dmitri.shuralyov.com/state latest
go: finding github.com/shurcooL/users latest
go: finding github.com/bradfitz/go-smtpd latest
go: finding github.com/gregjones/httpcache latest
go: finding golang.org/x/time latest
go: finding github.com/shurcooL/highlight_go latest
go: finding github.com/shurcooL/httpgzip latest
go: finding github.com/shurcooL/gofontwoff latest
go: finding github.com/shurcooL/httpfs latest
go: finding github.com/coreos/go-systemd latest
go: finding github.com/shurcooL/httperror latest
go: finding github.com/golang/lint latest
go: finding github.com/flynn/go-shlex latest
go: github.com/golang/lint@v0.0.0-20190409202823-959b441ac422: parsing go.mod: unexpected module path «golang.org/x/lint»
go: sourcegraph.com/sourcegraph/go-diff@v0.5.1: parsing go.mod: unexpected module path «github.com/sourcegraph/go-diff»
go: finding golang.org/x/tools v0.0.0-20190114222345-bf090417da8b
go: finding github.com/shurcooL/issues latest
go: finding github.com/shurcooL/reactions latest
go: finding github.com/shurcooL/gopherjslib latest
go: finding github.com/shurcooL/issuesapp latest
go: finding golang.org/x/perf latest
go get: error loading module requirements
The text was updated successfully, but these errors were encountered:
frederikhors commented Jun 21, 2019
Execute go get -u github.com/gobuffalo/buffalo-auth outside project folder.
If it works please close this issue.
jameswang2015 commented Sep 11, 2019
I get the same issue, and I run go get command at $HOME folder. Please advise.
zwang-mac:
zwang$ go get gitlab.vm.domaintools.net/backend/gatheringsystem/remington go: finding gitlab.vm.domaintools.net/backend/gatheringsystem/remington latest go: finding github.com/beorn7/perks v1.0.1 go: finding github.com/googleapis/gax-go/v2 v2.0.5 go: finding golang.org/x/sys v0.0.0-20190507160741-ecd444e8653b go: finding golang.org/x/sys v0.0.0-20190801041406-cbf593c0f2f3 go: finding golang.org/x/sys v0.0.0-20190509141414-a5b02f93d862 go: finding golang.org/x/net v0.0.0-20190503192946-f4e77d36d62c go: finding golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 go: finding golang.org/x/tools v0.0.0-20190506145303-2d16b83fe98c go: finding google.golang.org/appengine v1.5.0 go: finding golang.org/x/lint v0.0.0-20190409202823-959b441ac422 go: finding golang.org/x/net v0.0.0-20190108225652-1e06a53dbb7e go: finding github.com/hashicorp/golang-lru v0.5.1 go: finding github.com/knq/sysutil v0.0.0-20181215143952-f05b59f0f307 go: finding github.com/gobwas/httphead v0.0.0-20180130184737-2c6c146eadee go: finding github.com/golang/mock v1.3.1 go: finding go.opencensus.io v0.21.0 go: finding honnef.co/go/tools v0.0.0-20190418001031-e561f6794a2a go: finding cloud.google.com/go v0.34.0 go: finding google.golang.org/api v0.8.0 go: finding rsc.io/binaryregexp v0.2.0 go: finding github.com/json-iterator/go v1.1.7 go: finding gitlab.vm.domaintools.net/backend/gatheringsystem/gatherc/v3 v3.3.2 go: finding cloud.google.com/go v0.38.0 go: gitlab.vm.domaintools.net/backend/gatheringsystem/gatherc/v3@v3.3.2: unknown revision gatherc/v3.3.2 go: finding github.com/gobwas/pool v0.2.0 go: finding github.com/gobwas/ws v1.0.0 go: finding google.golang.org/genproto v0.0.0-20190801165951-fa694d86fc64 go: finding go.opencensus.io v0.22.0 go: finding golang.org/x/tools v0.0.0-20190628153133-6cdbf07be9d0 go: finding github.com/google/pprof v0.0.0-20190515194954-54271f7e092f go: finding cloud.google.com/go/datastore v1.0.0 go: finding github.com/mailru/easyjson v0.0.0-20180823135443-60711f1a8329 go: finding github.com/jstemmer/go-junit-report v0.0.0-20190106144839-af01ea7f8024 go: finding google.golang.org/genproto v0.0.0-20190502173448-54afdca5d873 go: finding google.golang.org/grpc v1.21.1 go: finding google.golang.org/grpc v1.20.1 go: finding github.com/mailru/easyjson v0.0.0-20190403194419-1ea4449da983 go: finding github.com/google/martian v2.1.0+incompatible go: finding golang.org/x/exp v0.0.0-20190510132918-efd6b22b2522 go: error loading module requirements
sio4 commented Jul 15, 2022
outdated. closing, but please feel free to reopen the issue if someone need help for the same issue.
Footer
© 2023 GitHub, Inc.
You can’t perform that action at this time.
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.
Источник