Closed yminsky closed 12 years ago
For what it's worth, this was resolved by blowing away my .opam directory and installing from scratch.
The current CURL backend is still not able to see changes upstream (this will change soon), so a possible way to fix that is to delete ~/.opam/repo/default/opam/*
and run 'opam update
again (or you can just remove lwt and ocsigen there, as they are the one causing the issue)
This should be fixed in the newly released 0.4.0
When I try to update opam, I get the following error:
~ $ opam update