[opam-commits] [Passed] mirage/opam-repository#434 (fix-mirage-multiremove - 800a4ef)

Travis CI notifications at travis-ci.org
Wed Feb 12 16:02:49 GMT 2014

Build Update for mirage/opam-repository

Build: #434
Status: Passed

Duration: 4 minutes and 58 seconds
Commit: 800a4ef (fix-mirage-multiremove)
Author: Anil Madhavapeddy
Message: Experimental fix for mirage/mirage#221

This leaves a stray binary after an uninstall, but fixes the
situation where the `mirage` binary attempts to upgrade itself
(due to invoking OPAM, which installs some optional dependencies,
which then proceed to try and recompile mirage).

The only long-term fix is to lift `mirage` into being a host-level
tool and not tracked by the same tool it uses to install libraries,
but for the moment renaming the active `mirage` binary to `mirage.old`
on uninstall should do the trick.

View the changeset: https://github.com/mirage/opam-repository/compare/fe447c204afd^...800a4ef62b14

View the full build log and details: https://travis-ci.org/mirage/opam-repository/builds/18737907


You can configure recipients for build notifications in your .travis.yml file. See http://about.travis-ci.org/docs/user/build-configuration

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/opam-commits/attachments/20140212/36d8dca8/attachment.html>

More information about the Opam-commits mailing list