Closed GoogleCodeExporter closed 9 years ago
Agreed. This needs to be handled more gracefully. I think a quick fix will be
to add a "--force" option, to simply ignore all errors, to allow for a way to
proceed for users bumping into this issue. Not so elegant, but it will at least
be quick to implement. I'll also open a new issue regarding the best way to
handle these kinds of errors.
Original comment by ekb...@gmail.com
on 24 Feb 2011 at 3:01
Fixed in changeset 296:a3acaa6dc936
There is now a --ignore option to 'update' that makes the process continue
after errors. Also, any errors are presented in a nicer way (not as stack
dumps).
Please verify that the fix works.
Original comment by ekb...@gmail.com
on 27 Feb 2011 at 4:26
I'm currently on vacation, but I will have a chance to try the new fix
on Monday. Thanks!
Original comment by fleeingt...@gmail.com
on 2 Mar 2011 at 2:13
Assuming verified.
Original comment by ekb...@gmail.com
on 20 Aug 2011 at 9:48
Original issue reported on code.google.com by
fleeingt...@gmail.com
on 21 Feb 2011 at 3:00