Closed edwintorok closed 10 years ago
I can confirm that (using opam 1.1.1 from Debian unstable, which hasn't changed recently). It looks like the solver does not take installed packages into account. Using aspcud doesn't change the issue.
@Emm it makes sense that aspcud doesn't change this: the solver actually returns the installed set that we should get to ; then it's OPAM which does a diff to extract the actions to get from the current state to there while keeping consistency. So it must be a bug in that part.
00:00.108 001230 STATE INSTALLED : {..........}
is right so the error would be at the graph_of_actions
step...
Superseded by #1683
I did an 'opam update' and got this: 144 to install | 0 to reinstall | 0 to upgrade | 0 to downgrade | 0 to remove
That looks suspicious, doing an 'opam upgrade' wants to do an install too (not a reinstall): [....]
$ opam --version 1.1.1
If I tell it to go ahead then it fails because ocamlfind is already installed. Some debug output: