"safe write of manifest and lock: error while writing out vendor tree: error while exporting"...

[tomwilkie]

Starting a fresh project that imports github.com/weaveworks/common/server, I get the following error:

$ dep init
Cached golang.org/x/net
Cached github.com/weaveworks/common
Cached github.com/mgutz/ansi
Cached github.com/armon/go-socks5
Cached golang.org/x/tools
Cached github.com/Sirupsen/logrus
Cached github.com/grpc-ecosystem/grpc-opentracing
Cached github.com/golang/protobuf
Cached github.com/opentracing-contrib/go-stdlib
Cached github.com/beorn7/perks
Cached github.com/prometheus/client_model
Cached github.com/prometheus/common
Cached github.com/prometheus/client_golang
Cached github.com/matttproud/golang_protobuf_extensions
Cached github.com/prometheus/procfs
Cached github.com/weaveworks-experiments/loki
safe write of manifest and lock: error while writing out vendor tree: error while exporting github.com/mwitkow/go-grpc-middleware: /var/folders/_b/ktq_dxhx0nbbw7gjtdzb3tn40000gn/T/dep051154450/vendor/github.com/mwitkow/go-grpc-middleware/README.md already exists, no checkout

[tomwilkie]

Error persists if I blow away by $GOPATH/pkg/dep cache.

[jstemmer]

Are you using a case-insensitive filesystem by any chance? The repo at https://github.com/mwitkow/go-grpc-middleware has both a README.MD and README.md file.

[tomwilkie]

Yeah, I'm on a Mac.

$ cd $GOPATH/pkg/dep/sources/https---git.luolix.top-mwitkow-go-grpc-middleware/
$ git status
HEAD detached at dbe298b
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	typechange: README.MD

no changes added to commit (use "git add" and/or "git commit -a")

[tomwilkie]

@mwitkow, did you mean to checkin two files that differ only by case?

[tomwilkie]

I guess this isn't really a bug in dep. An error along the lines of "Error running git foo in dir bar: ..." would have been nice. But not a big deal, I'll close.

[sdboyer]

Unfortunately, the error we have there is the one that's passed all the way back up from git itself. While we could probably do better with classifying the general type of error (e.g., "this came from git!"), and I hope we can tackle such things with #288, it's probably impractical to improve the content of the error message itself.