You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have conduit-lwt-unix (1.0.0) installed, and try to use the ogit binary provided by git-unix (1.11.2) [all using OCaml-4.04.2].
When executing ogit clone https://github.com/hannesm/duration.git, I receive an error Fatal error: exception (Failure "Ssl not available")
When I manually setenv CONDUIT_TLS native and rerun the command, it succeeds.
This seems to be a regression: I remember in earlier days the autodiscovery was done at compile time, and there shouldn't be a runtime error, since conduit-lwt-unix links a TLS implementation and could work appropriately. Maybe this is related to recent build system changes?
The text was updated successfully, but these errors were encountered:
See #238, this is fixed on master. I'm trying to make a release, but the SSL and launchd backends are broken on master, so I'm also fixing the CI to catch these kind of errors earlier... Hopefully this long journey should be ending soon and a release will happen.
@samoht thanks! closing this then. sorry, I didn't see #238 when browsing the issues/PRs, since it is already closed (and I don't watch this repository). Hopefully awaiting a new release really soon now then :)
I have
conduit-lwt-unix
(1.0.0) installed, and try to use theogit
binary provided bygit-unix
(1.11.2) [all using OCaml-4.04.2].When executing
ogit clone https://github.com/hannesm/duration.git
, I receive an errorFatal error: exception (Failure "Ssl not available")
When I manually
setenv CONDUIT_TLS native
and rerun the command, it succeeds.This seems to be a regression: I remember in earlier days the autodiscovery was done at compile time, and there shouldn't be a runtime error, since
conduit-lwt-unix
links a TLS implementation and could work appropriately. Maybe this is related to recent build system changes?The text was updated successfully, but these errors were encountered: