From 8c89f8feaca5e12001e5b8cfc9736fbc10091af7 Mon Sep 17 00:00:00 2001
From: Ushitora Anqou <ushitora@anqou.net>
Date: Mon, 9 Mar 2026 08:43:57 +0900
Subject: [PATCH] use newer mirage-crypto-rng-eio

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.
---
 dune-project                         | 2 +-
 opentelemetry-client-cohttp-eio.opam | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dune-project b/dune-project
index e8f834fd..e0f924ee 100644
--- a/dune-project
+++ b/dune-project
@@ -214,7 +214,7 @@
   (mtime
    (>= "1.4"))
   ca-certs
-  mirage-crypto-rng-eio
+  mirage-crypto-rng
   ambient-context-eio
   (opentelemetry
    (= :version))
diff --git a/opentelemetry-client-cohttp-eio.opam b/opentelemetry-client-cohttp-eio.opam
index 6ac2740c..1f3bfcad 100644
--- a/opentelemetry-client-cohttp-eio.opam
+++ b/opentelemetry-client-cohttp-eio.opam
@@ -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}