On 29/03/2018 14:02, Adam Steen wrote: > opam pin add mirage https://github.com/hannesm/mirage.git#ld-pkg-config > mirage is now git-pinned to > https://github.com/hannesm/mirage.git#ld-pkg-config > > [mirage] https://github.com/hannesm/mirage.git#ld-pkg-config updated > [mirage] Installing new package description from > https://github.com/hannesm/mirage.git#ld-pkg-config > > mirage needs to be installed. > Your request can't be satisfied: > - mirage.dev~solo5 is not available because the package is pinned to > https://github.com/hannesm/mirage.git#ld-pkg-config, version dev~solo5.
ok, maybe a `opam pin add mirage.dev~solo5 https://github.com/hannesm/mirage.git#ld-pkg-config` ? i.e. specify the version number of mirage explicitly.. I'm not entirely sure how opam behaves in such a setting (IIUC, on OpenBSD you still don't use any external solver). hannes _______________________________________________ MirageOS-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/mirageos-devel
