Closed Flight310 closed 7 years ago
I wonder if we should just move conduit + cohttp to ppx to avoid all this headache.
@ivg are you ok with that?
@rgrinberg, I can only dream about this!
@ivg OK, then we need to heckle the TLS devs first.
Obviously need to move cohttp and conduit to ppx!
@vbmithr already done!
Need to release conduit though.
Well done. Actually I was able to install latest cohttp, conduit has not been yet released but not a problem :) Thanks!
It looks like this is preventing conduit/cohttp from being installable through opam under 4.03.0.
@hcarty will release this weekend
@rgrinberg :+1:
new version of conduit was released. this is no longer an issue.
I use cohttp with latest Core everyday. Closing.
There seems to be a conflict with "conduit" with the latest versions of other packages. This prevents installing the cohttp package (which relies on conduit) with the latest version of other things in opam.
This is preventing installing dependencies for the Real World OCaml book, per instructions here: https://github.com/realworldocaml/book/wiki/Installation-Instructions which is very confusing.
Is there some way you can modify your conduit not to give huge numbers of scary downgrade warnings? For now, I'll simply not install cohttp & conduit. I have installed every other dependency of cohttp without any downgrade warnings.
This seems to be related to the commit here: https://github.com/mirage/ocaml-conduit/commit/4f876e517b0d8ee2a4bdcbad259a8d87bcfe9d60 but it is not explained in the commit notes WHY this restriction was applied.
Many thanks!