4 ms·

> When requested to install a second package with overlapping dependencies as a previous package, it would try reinstalling all dependencies This was unfortuna

by avsm 12y ago

> When requested to install a second package with overlapping dependencies as a previous package, it would try reinstalling all dependencies This was unfortunately a mistake made by upstream Debian. Rather than reimplement the constraint solver badly, we use the Aspcud external solver. An upgrade of Aspcud changed its command-line interface, and OPAM 1.1.0 wasn't upgraded to OPAM 1.1.1 at the same time (which detected the new version of Aspcud and worked with it). A similar issue (to do with the libdose interface) has been in the Ubuntu package ages and not addressed by upstream despite a detailed bug report: https://bugs.launchpad.net/ubuntu/+source/opam/+bug/1401346 https://bugs.launchpad.net/ubuntu/+source/opam/+bug/1401346 > Searching online found recommendations to get the latest version from Github What else could we recommend? It's really frustrating to know that a source-compiled OPAM works fine, but that the packaged binary versions are broken and our only recourse is to wait six months for the next OS release of Ubuntu. On the bright side, the OPAM 1.2.x series has been very stable and is now making its way upstream, so this is hopefully a temporary issue.

e12e 12y ago
That explains a lot. I thought opam was behaving better now, than I recall it did at some random point in the past. I'm really grateful to everyone doing all this work. This is a typical example of the kind of "excitement" mixing distro package managers and language package managers can lead to. The only recourse is to file a bug, maybe provide a backport if feasible, and move on -- and have everyone (package maintainers, distros) be a little wiser, and (hopefully) everything working on the next release. Anyway, I see I have opam in my ~/bin -- so clearly I've compiled it myself at some point. No wonder, as I'm still running stable on this laptop: https://packages.debian.org/search?keywords=opam&searchon=names&suite=all&section=all https://packages.debian.org/search?keywords=opam&searchon=na... Maybe there should be a note in the wiki about it, although it should be resolved when jessie is out?: https://wiki.debian.org/OCaml https://wiki.debian.org/OCaml (Yeah, I know, it's a wiki. I could just add it. I don't feel quite confident enough to go and clutter such a short little page, though. Different if there's a page where "someone is wrong on the internet".)
AceJohnny2 12y ago
Thanks for your work! In that particular timeframe (Sept/Oct 2014), the Debian maintainer just hadn't uploaded a newer version of the package: https://tracker.debian.org/pkg/opam https://tracker.debian.org/pkg/opam It's a pity, because I think Debian's Experimental section would've been ideal for this. I've been using Debian long enough that I'm a bit ashamed not to be able to package things on my own yet...

by avsm 12y ago

e12e 12y ago

That explains a lot. I thought opam was behaving better now, than I recall it did at some random point in the past. I'm really grateful to everyone doing all this work. This is a typical example of the kind of "excitement" mixing distro package managers and language package managers can lead to. The only recourse is to file a bug, maybe provide a backport if feasible, and move on -- and have everyone (package maintainers, distros) be a little wiser, and (hopefully) everything working on the next release. Anyway, I see I have opam in my ~/bin -- so clearly I've compiled it myself at some point. No wonder, as I'm still running stable on this laptop: https://packages.debian.org/search?keywords=opam&searchon=names&suite=all&section=all https://packages.debian.org/search?keywords=opam&searchon=na... Maybe there should be a note in the wiki about it, although it should be resolved when jessie is out?: https://wiki.debian.org/OCaml https://wiki.debian.org/OCaml (Yeah, I know, it's a wiki. I could just add it. I don't feel quite confident enough to go and clutter such a short little page, though. Different if there's a page where "someone is wrong on the internet".)

AceJohnny2 12y ago

Thanks for your work! In that particular timeframe (Sept/Oct 2014), the Debian maintainer just hadn't uploaded a newer version of the package: https://tracker.debian.org/pkg/opam https://tracker.debian.org/pkg/opam It's a pity, because I think Debian's Experimental section would've been ideal for this. I've been using Debian long enough that I'm a bit ashamed not to be able to package things on my own yet...