Dep: grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export k8s.io/apiserver: unable to update repository: From https://github.com/kubernetes/apiserver

Created on 15 Feb 2019  路  7Comments  路  Source: golang/dep

What version of dep are you using (dep version)?

鈺扳攢>$ dep version
dep:
 version     : v0.5.0
 build date  : 2018-07-26
 git hash    : 224a564
 go version  : go1.10.3
 go compiler : gc
 platform    : linux/amd64
 features    : ImportDuringSolve=false

What dep command did you run?

dep ensure -v

(after having removed the vendor/ directory completely, because if I don't I get a different error simllar to issue #1439)

What did you expect to see?

dep ensure -v succeeds.

What did you see instead?

鈺扳攢>$ dep ensure -v
(1/91) Wrote github.com/davecgh/[email protected]
(2/91) Wrote github.com/beorn7/perks@master
(3/91) Wrote github.com/coreos/[email protected]
(4/91) Wrote github.com/emicklei/[email protected]
(5/91) Wrote github.com/appscode/[email protected]
(6/91) Wrote github.com/gobuffalo/[email protected]
(7/91) Wrote github.com/go-logr/[email protected]
(8/91) Wrote github.com/google/gofuzz@master
(9/91) Wrote github.com/opencontainers/[email protected]
(10/91) Wrote github.com/blang/[email protected]
(11/91) Wrote github.com/coreos/[email protected]
(12/91) Wrote google.golang.org/[email protected]
(13/91) Wrote github.com/docker/[email protected]
(14/91) Wrote sigs.k8s.io/[email protected]
(15/91) Wrote github.com/go-logr/logr@master
(16/91) Wrote github.com/pborman/[email protected]
(17/91) Wrote github.com/google/[email protected]
(18/91) Wrote github.com/googleapis/[email protected]
(19/91) Wrote github.com/GoogleCloudPlatform/[email protected]
(20/91) Wrote github.com/ghodss/[email protected]
(21/91) Wrote k8s.io/code-generator@master
(22/91) Wrote github.com/coreos/[email protected]
(23/91) Wrote cloud.google.com/[email protected]
(24/91) Wrote github.com/dgrijalva/[email protected]
(25/91) Wrote github.com/golang/glog@master
(26/91) Wrote k8s.io/[email protected]
(27/91) Wrote github.com/coreos/go-systemd@v18
(28/91) Wrote github.com/gregjones/httpcache@master
(29/91) Wrote github.com/coreos/pkg@v4
(30/91) Wrote google.golang.org/genproto@master
(31/91) Wrote google.golang.org/[email protected]
(32/91) Wrote github.com/gogo/[email protected]
(33/91) Wrote github.com/modern-go/[email protected]
(34/91) Wrote sigs.k8s.io/[email protected]
(35/91) Wrote golang.org/x/tools@master
(36/91) Wrote github.com/petar/GoLLRB@master
(37/91) Wrote github.com/matttproud/[email protected]
(38/91) Wrote github.com/json-iterator/[email protected]
(39/91) Wrote github.com/peterbourgon/[email protected]
(40/91) Wrote github.com/hashicorp/[email protected]
(41/91) Wrote gopkg.in/[email protected]
(42/91) Wrote k8s.io/[email protected]
(43/91) Wrote k8s.io/[email protected]
(44/91) Wrote sigs.k8s.io/[email protected]
(45/91) Wrote k8s.io/utils@master
(46/91) Wrote k8s.io/[email protected]
(47/91) Wrote gopkg.in/fsnotify.v1 (from https://github.com/fsnotify/fsnotify.git)@v1.4.7
(48/91) Wrote github.com/modern-go/[email protected]
(49/91) Wrote github.com/google/btree@master
(50/91) Wrote sigs.k8s.io/[email protected]
(51/91) Wrote github.com/pkg/[email protected]
(52/91) Wrote github.com/google/[email protected]
(53/91) Wrote github.com/markbates/[email protected]
(54/91) Wrote k8s.io/kube-openapi@master
(55/91) Wrote github.com/jinzhu/copier@master
(56/91) Wrote github.com/onsi/[email protected]
(57/91) Wrote github.com/xiang90/[email protected]
(58/91) Failed to write k8s.io/apiserver@master
(59/91) Failed to write k8s.io/[email protected]
(60/91) Failed to write k8s.io/[email protected]
(61/91) Failed to write sigs.k8s.io/[email protected]
(62/91) Failed to write github.com/prometheus/[email protected]
(63/91) Failed to write github.com/kubernetes-sigs/application@51c1b68e024fd1ddad509060d80e52935cfb19a2
(64/91) Failed to write k8s.io/gengo@master
(65/91) Failed to write go.uber.org/[email protected]
(66/91) Failed to write gopkg.in/tomb.v1@v1
(67/91) Failed to write github.com/golang/[email protected]
(68/91) Failed to write gopkg.in/[email protected]
(69/91) Failed to write golang.org/x/sys@master
(70/91) Failed to write golang.org/x/net@master
(71/91) Failed to write golang.org/x/crypto@master
(72/91) Failed to write github.com/hpcloud/[email protected]
(73/91) Failed to write github.com/onsi/[email protected]
(74/91) Failed to write go.uber.org/[email protected]
grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export k8s.io/apiserver: unable to update repository: From https://github.com/kubernetes/apiserver
 ! [rejected]          kubernetes-1.12.0        -> kubernetes-1.12.0  (would clobber existing tag)
 ! [rejected]          kubernetes-1.12.0-beta.2 -> kubernetes-1.12.0-beta.2  (would clobber existing tag)
 ! [rejected]          kubernetes-1.12.0-rc.1   -> kubernetes-1.12.0-rc.1  (would clobber existing tag)
 ! [rejected]          kubernetes-1.12.0-rc.2   -> kubernetes-1.12.0-rc.2  (would clobber existing tag)
 ! [rejected]          kubernetes-1.12.1-beta.0 -> kubernetes-1.12.1-beta.0  (would clobber existing tag)
: command failed: [git fetch --tags --prune origin]: exit status 1

Most helpful comment

Just ran into a similar issue, deleting $GOPATH/pkg/dep/sources solved it for me.

All 7 comments

Can you post your Gopkg.toml file or the repository you're attempting to use?

It seems like the Kubernetes download already has Git tags, and now the remote is saying there are new tags, and we don't handle that situation well. You could try pointing at a revision, or clobbering the cached version of Kubernetes, which should be somewhere in $GOPATH/pkg/dep.

Sadly, no, I can not disclose the Gopkg.toml. SRY.

Given the information you requested, I suppose that some of the prior errors (like issue #1439) may have left the cached repos in $GOPATH/pkg/dep/sources a state where tags were already downloaded.

While it's a far cry from a resolution, I think it would help tremendously if the error message also disclosed the local filesystem path to the failing repository. Otherwise, without knowing the internals of dep, I will as user have no clue to which repo is failing.

So basically "unable to update repository" should be replaced with an error message that points to where it exists on disk?

I totally wouldn't mind having that extra bit of information there!

Just ran into a similar issue, deleting $GOPATH/pkg/dep/sources solved it for me.

i am also facing this issue,
grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export google.golang.org/genproto:
searched a lot about this, almost everyone says delete vendor directory or source directory. I am facing this error while running Dockerfile. Dont know how to delete it from docker containers.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!

Was this page helpful?
0 / 5 - 0 ratings