I already fetch the package, but why this happen

[filosottile]

I already fetch the package, but why this happen

[mholt]

I've seen this happen once or twice too. But running it again, doesn't seem to happen.

$ vendorcheck ./...
... (bunch of dependencies not vendored) ...
[!] dependency not vendored: github.com/miekg/dns

$ gvt fetch <a few of the dependencies listed above>

$ gvt fetch github.com/miekg/dns
2017/05/27 10:32:25 Fetching: github.com/miekg/dns

$ vendorcheck ./...
... (bunch of dependencies not vendored) ...
[!] dependency not vendored: github.com/miekg/dns
... (bunch more dependencies not vendored) ...

It's in a different place in the package list (it was last the first time, in the middle the next time). Notice the dns package was still reported unvendored. But then I gvt fetch'ed a few other dependencies and then again:

$ vendorcheck ./...
[!] dependency not vendored: github.com/flynn/go-shlex
[!] dependency not vendored: github.com/jimstudt/http-authentication/basic
[!] dependency not vendored: github.com/hashicorp/go-syslog
[!] dependency not vendored: github.com/gorilla/websocket

In other words, somehow it seems to have resolved itself even without doing anything related to that package.

[FiloSottile]

I think vendorcheck is correct here, but it's subtle and I should document it.

If you vendor package A, then import package B, which is not vendored, and package B imports package A, it will not import your vendored copy. It will "escape".