Skip to content
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

Use gomod go get v2 error #1042

Closed
644262163 opened this issue Sep 28, 2019 · 9 comments
Closed

Use gomod go get v2 error #1042

644262163 opened this issue Sep 28, 2019 · 9 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@644262163
Copy link

I have a project that I want to import this project

go version

go version go1.13 linux/amd64

I tried to use all five ways and failed

1

$ go get sigs.k8s.io/kubebuilder@v2.0.0

go get sigs.k8s.io/kubebuilder@v2.0.0: sigs.k8s.io/kubebuilder@v2.0.0: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

2

$ go get sigs.k8s.io/kubebuilder/v2@v2.0.0

go get sigs.k8s.io/kubebuilder/v2@v2.0.0: sigs.k8s.io/kubebuilder@v2.0.0: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

3

$ cat go.mod

module test
go 1.13
require sigs.k8s.io/kubebuilder v2.0.0+incompatible

$ go get

verifying sigs.k8s.io/kubebuilder@v2.0.0+incompatible/go.mod: sigs.k8s.io/kubebuilder@v2.0.0+incompatible/go.mod: reading https://sum.golang.org/lookup/sigs.k8s.io/kubebuilder@v2.0.0+incompatible: 410 Gone

4

$ cat go.mod

module test
go 1.13
require sigs.k8s.io/kubebuilder v2.0.0

$ go get

/test/go.mod:3: require sigs.k8s.io/kubebuilder: version "v2.0.0" invalid: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

5

$ cat go.mod

module test
go 1.13
require sigs.k8s.io/kubebuilder/v2 v2.0.0

$ go get

go: sigs.k8s.io/kubebuilder/v2@v2.0.0: go.mod has non-.../v2 module path "sigs.k8s.io/kubebuilder" (and .../v2/go.mod does not exist) at revision v2.0.0

/kind bug

@644262163 644262163 added the kind/bug Categorizes issue or PR as related to a bug. label Sep 28, 2019
@camilamacedo86
Copy link
Member

Could you try to use go 1.12? I believe that the version 1.13 is not supported yet.

@DirectXMan12
Copy link
Contributor

Go 1.13 is supported. This is a bug.

@DirectXMan12
Copy link
Contributor

/priority backlog

backlog since we do binary releases and don't expose a public API.

We should fix this eventually, though.

@camilamacedo86
Copy link
Member

Great to know that it is supporting 1.13 already :-)

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 10, 2020
@camilamacedo86
Copy link
Member

hi @DirectXMan12,

When this issue was raised the project was not supporting go 1.13+ as described above. However, we made this update in the PR; #1135

So, we can close this one :-) less -1.

@camilamacedo86
Copy link
Member

/assing @camilamacedo86

@camilamacedo86
Copy link
Member

/close

@k8s-ci-robot
Copy link
Contributor

@camilamacedo86: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

5 participants