dep prune: lock hash doesn't match

[tomwilkie]

Happens when I update a single dependancy:

Toms-MacBook-Pro:cortex twilkie$ dep ensure github.com/weaveworks/common@grpc_http_metrics
Toms-MacBook-Pro:cortex twilkie$ dep prune
lock hash doesn't match

Goes away if I do a dep ensure.

[tomwilkie]

Also of note, I had to go and manually update the cached repo for github.com/weaveworks/common, as I was getting:

$ dep ensure github.com/weaveworks/common@grpc_http_metrics
ensure Solve(): No versions of github.com/weaveworks/common met constraints:
	master: Could not introduce github.com/weaveworks/common@master, as it is not allowed by constraint grpc_http_metrics from project github.com/weaveworks/cortex.
	context: Could not introduce github.com/weaveworks/common@context, as it is not allowed by constraint grpc_http_metrics from project github.com/weaveworks/cortex.
	grpc_http_metrics: Unable to update checked out version: fatal: reference is not a tree: 37bdded08835f193231acccdc7b18cbb748bcd73

	log-users: Could not introduce github.com/weaveworks/common@log-users, as it is not allowed by constraint grpc_http_metrics from project github.com/weaveworks/cortex.

Which looks like #639 again.

[sdboyer]

Happens when I update a single dependancy:

Hmm, seems like a regression on ensure. We should probably update our test harness to enforce the invariant that commands exit with the same lock inputs hash that it wrote out to the lockfile.

Also of note, I had to go and manually update the cached repo for github.com/weaveworks/common, as I was getting:

I'm gonna try to find time today to track this down personally, we can't leave it sit.

[tomwilkie]

Thanks. I should have some more time to spend on dep next week I hope.

[sdboyer]

the underlying issue with dep ensure is now fixed; closing this.