further mirage-crypto 0.11.0 breaking reverse dependencies:

[hannesm]

in order to fix #23237 revdeps

(a) Mirage_crypto_rng_lwt is now in the separate package mirage-crypto-rng-lwt (b) Mirage_crypto_rng_unix.initialize signature changed

• dream
• hyper
• jose
• letsencrypt
• rfc6287
• ssh-agent
• twostep

And in mirage-block-ccm: now AES.CCM16, no AES.CCM anymore

[ulrikstrid]

Just to be clear, for tests I can just do this if I want to upgrade right?

let () =
  Mirage_crypto_rng.default_generator () |> Mirage_crypto_rng_unix.initialize

[hannesm]

@ulrikstrid thanks for reaching out, I plan to write a small note into the final changelog, but basically your

let () = Mirage_crypto_rng_unix.initialize ()

will now be:

let () = Mirage_crypto_rng_unix.initialize (module Mirage_crypto_rng.Fortuna)

The change is motivated by uniformity of the initialize function (present for _unix, _eio, _async, _mirage, _lwt) -- now passing the desired RNG module explicitly.

[hannesm]

The CI failures are unrelated. Good to merge.

[kit-ty-kate]

Thanks