Thanks. Filling in the template from https://wiki.ubuntu.com/StableReleaseUpdates :
[Impact] * `opam` will only work on first `init` and `install` commands, but break severely as soon as another action is attempted (upgrade, new install...) -- its state becomes broken and it's unusable unless you start from scratch. * We don't have a simple patch for the bug, because the way we use the Dose library had been rewritten _before_ a change to Dose broke (older) OPAM's behaviour, and the cleaner rewrite did'nt trigger it -- indeed the breakage never happened in the upstream's timeline (which also explains how it was overlooked). [Test Case] `opam init; opam install lwt; opam install utop`: OPAM tries to reinstall packages that are already installed and breaks. [Regression Potential] * the new version, released in october, hasn't seen any important bugs * for what it's worth, it's been included in the Debian Jessie freeze, with no issue so far * no packages depend on OPAM as far as I know, so consequences are limited * given the current state of the package, it can only get better [Other Info] In case pushing the newer version is really not an option, I'd even be in favor of having it pulled off utopic rather than left in the current state: it doesn't reflect on the quality of our software, and we had to include warnings about this bug in our troubleshooting pages. Thanks for your time ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401346 Title: OPAM 1.1.1-1build3 (utopic) is broken because compiled with an incompatible version of libdose3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opam/+bug/1401346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
