Skip to content
This repository has been archived by the owner on Feb 26, 2019. It is now read-only.

What to do when a dependency revision is removed? #203

Open
ronna-s opened this issue Apr 10, 2015 · 2 comments
Open

What to do when a dependency revision is removed? #203

ronna-s opened this issue Apr 10, 2015 · 2 comments

Comments

@ronna-s
Copy link

ronna-s commented Apr 10, 2015

I may be using godep wrong, but the README doesn't really explain how to work with this tool. I saved all the dependencies successfully a while ago using godep save. But as some of the repositories have been moved, I can't execute godep update or restore anymore.

@freeformz
Copy link

ATM you need to manually prune out the olds locations and then godep save the new deps. You may be able to get away with doing a godep restore, blowing away $project/Godeps, updating the deps in your code and doing a new godep save. Or at least that's what I would try first.

@ronna-s
Copy link
Author

ronna-s commented Apr 13, 2015

It sounds very unreasonable. If you had a working tree once and you saved it, then at least on the technical level you have everything you need to deploy your project and update specific packages. Why the hassle? Also, godep doesn't tell you what dependencies are missing, I just receive random errors.

for instance:
godep restore
godep: unable to detect version control system for code.google.com/ path

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants