simon/ocaml-opentelemetry
1
0
Fork 0
mirror of https://github.com/ocaml-tracing/ocaml-opentelemetry.git synced 2026-03-10 04:35:46 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

use newer mirage-crypto-rng-eio
Some checks are pending
format / format (push) Waiting to run
Details
build / build (4.08.x, ubuntu-latest) (push) Waiting to run
Details
build / build (4.13.x, ubuntu-latest) (push) Waiting to run
Details
build / build (5.0.x, ubuntu-latest) (push) Waiting to run
Details
build / build (5.3.x, ubuntu-latest) (push) Waiting to run
Details

Browse source 
Although I don't know why, mirage-crypo-rng package of >= 2.0.0 is released
but mirage-crypto-rng-eio is not (it's stuck at 1.2.0).

cf. https://opam.ocaml.org/packages/mirage-crypto-rng/mirage-crypto-rng.2.0.3/
cf. https://opam.ocaml.org/packages/mirage-crypto-rng-eio/mirage-crypto-rng-eio.1.2.0/

Currently, ocaml-opentelemetry depends on mirage-crypto-rng-eio, so
those who want to use mirage-crypto-rng >= 2.0.0 (like me) can't use
ocaml-opentelemetry.

This commit fixes this problem by replacing mirage-crypto-rng-eio with
mirage-crypto-rng in dune-project (thus in
opentelemetry-client-cohttp-eio.opam) to make ocaml-opentelemetry depend
on mirage-crypto-rng instead of mirage-crypto-rng-eio.
This commit is contained in:
Ushitora Anqou 2026-03-09 08:43:57 +09:00 • committed by Simon Cruanes
parent 31e9812b4f
commit 54dc4d0ef7
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
dune-project
View file

@ -214,7 +214,7 @@
(mtime
(>= "1.4"))
ca-certs
mirage-crypto-rng-eio
mirage-crypto-rng
ambient-context-eio
(opentelemetry
(= :version))

2
opentelemetry-client-cohttp-eio.opam
View file

@ -16,7 +16,7 @@ depends: [
"ocaml" {>= "5.00"}
"mtime" {>= "1.4"}
"ca-certs"
"mirage-crypto-rng-eio"
"mirage-crypto-rng"
"ambient-context-eio"
"opentelemetry" {= version}
"opentelemetry-client" {= version}