Open arvidj opened 1 year ago
Thanks for the report @arvidj. That is strange cohttp doesn't seem to be pulling in the ssl or tls dependency correctly in 5.0.0. I'll do some investigation.
Thanks, I'd be happy to provide more details if you there's something specific you need :)
Got bit by this again. This time with the package set:
- install conduit 6.2.0
- install mirage-crypto-pk 0.10.7
- install cohttp 4.1.2
- install conduit-lwt 6.2.0
- install x509 0.11.2
- install cohttp-lwt 4.1.2
- install tls 0.12.8
- install ca-certs 0.2.0
- install gitlab 0.1.7
- install conduit-lwt-unix 6.2.0
- install cohttp-lwt-unix 4.1.2
- install gitlab-unix 0.1.7
(from here).
I'm attempting to resolve it by forcing cohttp 4.0.0, that seems to work.
Any ideas on a more prinicipled approach to this problem? Shouldn't ocaml-gitlab
also depend on ssl or tls? Or is the idea that the user decides whether they want ssl or tls, as discussed here?
In my dune-project
, I have:
(depends
ocaml
dune
tezt
uri
(cohttp-lwt-unix (< 4.1.2))
(tls (< 0.13.0))
ISO8601
(gitlab (>= 0.1.7))
gitlab-unix)
Perhaps I should have tls-lwt
instead of tls
?
The idea is the user can choose which implementation they want. But it is a surprising error if you're just picking up this library to do something. A good solution would be to document the error message in the project README and show how to fix it plus a link to the discuss thread.
In my
dune-project
, I have:(depends ocaml dune tezt uri (cohttp-lwt-unix (< 4.1.2)) (tls (< 0.13.0)) ISO8601 (gitlab (>= 0.1.7)) gitlab-unix)
Perhaps I should have
tls-lwt
instead oftls
?
I would have tls-lwt
rather than tls
in that setup.
I'm getting errors like:
[error] No SSL or TLS support compiled into Conduit
with recent versions of
ocaml-gitlab
. I have made sure the tls package is installed.Here's my list of packages:
The problems go away when I restrict
cohttp
to< 5.0.0
. Here's the list of packages I get in this case: