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

glide install fails with alias: "The Remote does not match the VCS endpoint" #210

Closed
colemickens opened this issue Jan 6, 2016 · 8 comments

Comments

@colemickens
Copy link

My glide.yaml:

package: azkube
import:
- package: github.com/Azure/azure-sdk-for-go
  subpackages:
  - /arm/resources
- package: github.com/spf13/cobra
- package: code.google.com/p/go-uuid
  subpackages:
  - /uuid
- package: golang.org/x/crypto
  vcs: git
  repo: https://github.com/colemickens/crypto
  version: 147b0a0d44eaebb0e4b9c780d01b9af728575d49
  subpackages:
  - /pkcs12

Snippet of log from glide install:

[INFO] Fetching updates for golang.org/x/crypto.
[WARN] Update failed for golang.org/x/crypto: The Remote does not match the VCS endpoint
[WARN] Failed to set version on golang.org/x/crypto to 147b0a0d44eaebb0e4b9c780d01b9af728575d49: The Remote does not match the VCS endpoint

Error originates in source here: https://github.com/Masterminds/vcs/blob/master/repo.go

@colemickens
Copy link
Author

Apologies, it looks like this is due to me not clearing out the relevant repo under vendor/ before "switching" via the alias. I executed rm -rf vendor/ and then glide was able to install normally.

@bscott
Copy link

bscott commented May 28, 2017

I still get this even while removing vendor directory.

@sparkLogic
Copy link

Yes, I still see this error even after rm -rf vendor

@JeanMertz
Copy link

JeanMertz commented Jun 4, 2017

Getting the same error, even after rm:

[ERROR]	Failed to set version on github.com/sirupsen/logrus to : The Remote does not match the VCS endpoint
[ERROR]	Failed to set references: The Remote does not match the VCS endpoint (Skip to cleanup)

update rm -r ~/.glide did the trick 👍

@Connor-McGuinness
Copy link

We had the same problem and solved it by modifying the glide.yaml to case-strict match the VCS endpoint (github.com/Sirupsen/logrus became github.com/sirupsen/logrus) then clearing the glide cache (glide cc).

@bkleef
Copy link

bkleef commented Jun 8, 2017

Or try something like this:

glide cc; rm -rf ~/.glide; rm -rf vendor; rm glide.lock; glide install --force --strip-vendor

@sjansen
Copy link

sjansen commented Jul 19, 2017

For the benefit of anyone brought here by Google...

solution: sirupsen/logrus#553 (comment)
reason: sirupsen/logrus#570 (comment)

@ufukomer
Copy link

glide cc only 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants