Open diwakergupta opened 8 years ago
FYI, even after I add version information to glide.yaml
(copying over from glide.lock
after first run), I still get the same errors. cc/ @mattfarina to your comment in another issue, this has very high WTF-factor IMO.
@diwakergupta Have you stripped the VCS metadata from the projects in your vendor/
directory? I have an idea what this might be (and it may be a legitimate bug).
@mattfarina I tried with and without stripping VCS metadata -- get the same warnings.
@mattfarina any update on this? I'd love to start using glide, but am blocked behind this.
I have the same problem. I just created a new project and I included some deps:
package: testtt
import:
- package: github.com/spf13/pflag
- package: k8s.io/client-go
version: ^2.0.0-alpha.0
subpackages:
- kubernetes
- pkg/api
- pkg/api/errors
- pkg/api/meta
- pkg/api/unversioned
- pkg/api/v1
- pkg/apis/extensions/v1beta1
- pkg/fields
- pkg/runtime
- pkg/runtime/serializer
- pkg/util/strategicpatch
- rest
- tools/clientcmd
- package: k8s.io/kubernetes
version: ~1.4.x
subpackages:
- pkg/api/annotations
And I have the same problem when I run glide list
. I'm in Mac OS X 10.11.6 with glide version 0.12.3
from homebrew.
Same problem here!
I'm playing around with glide for dbxcli (https://github.com/dropbox/dbxcli). I deleted the vendor directory, then ran
glide init
followed byglide up
. Then runningglide list
shows me many warnings like:This is followed by a package list that contains many duplicates:
Are these known issues? There are definitely non-intuitive and surprising. Glide looks great but making new project onboarding seamless will be crucial for adoption.