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

git: no submodule mapping found in .gitmodules #150

Closed
zchee opened this issue Oct 7, 2016 · 6 comments
Closed

git: no submodule mapping found in .gitmodules #150

zchee opened this issue Oct 7, 2016 · 6 comments

Comments

@zchee
Copy link
Contributor

zchee commented Oct 7, 2016

Hi,
I tried go get github.com/digitalocean/doctl/cmd/doctl, occur error. the log is below.
FYI, it's the first fetch and also tried rm -rf doctl and re-fetch use git directly. same results.

fatal: no submodule mapping found in .gitmodules for path 'vendor/github.com/vektra/errors'

I don't know doctl repository history(did use submodule for the manage vendoring previous?), but it might exist junk submodule data on git tree.
go get command automatically fetch submodule with --recursive flag, and git clone --recursive will occur.
If git clone only, maybe not occur.

Anyway, If I'm not wrong(my git environment), I think we should solve it.

@zchee
Copy link
Contributor Author

zchee commented Oct 7, 2016

Or, it's github.com/vektra/errors issue?

@hholst80
Copy link

I have the same error. No comments from Digital Ocean?

@xmudrii
Copy link
Contributor

xmudrii commented Oct 17, 2016

It is known issue. As far as I know, @bryanl was looking into it, but I don't know did he made any progress with it. There was even some PRs that tried to fix it but it was out of luck.
You can just run command again and it should install it without any problem.
Take look at #42 for more insight about it.

@lapawa
Copy link

lapawa commented Dec 16, 2016

Have the same issue here. command:
$ go get github.com/digitalocean/doctl/cmd/doctl
exits with message:
$ fatal: no submodule mapping found in .gitmodules for path 'vendor/github.com/vektra/errors'

$ go version
go version go1.6.2 linux/amd64

@dch
Copy link

dch commented Feb 9, 2017

this hack #47 (comment) is enough to get the tool built, but from a production perspective skipping the tests is not really an ideal solution.

@zchee
Copy link
Contributor Author

zchee commented Mar 13, 2017

@xmudrii Ohh. Today, I understood that cause.
I'll send pull request later(maybe).

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

6 participants