You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the ignore: directive in glide.yaml to mark some package to be ignored.
When running glide up, this package is not downloaded by glide, but still gets written into glide.lock.
Later on, when running glide install, glide tries to fetch the ignored package.
I've recreated this behavior using the following simple setup:
@mattfarina indeed seems to be fixed - ignored package doesn't get into the lock file.
I tested with both the app/lib example above, as well as the real repo I've seen this happen in.
Hello,
I'm using the
ignore:
directive inglide.yaml
to mark some package to be ignored.When running
glide up
, this package is not downloaded by glide, but still gets written intoglide.lock
.Later on, when running
glide install
, glide tries to fetch the ignored package.I've recreated this behavior using the following simple setup:
The code at
app/main.go
importsgithub.com/myorg/lib
.The
glide.yaml
looks like this:Running
glide up
within theapp
folder, yields the followingglide.lock
file:Notably, the
github.com/myorg/lib
package is listed as an import.P.S., I'm using glide 0.10.2, but also recreated this with 0.11.0-dev.
The text was updated successfully, but these errors were encountered: