Jan Midtgaard

I believe there's some overlap between this PR and #29089.

Thanks! The proposed package `omni-irc` has a number of dependencies: ``` "omni-irc-sig" "omni-irc-conn" "omni-irc-engine" "omni-irc-io-tcp" "omni-irc-io-tls" {"os" != "win32"} "omni-irc-io-unixsock" {"os" != "win32"} "omni-irc-ui" "omni-irc-ui-notty" {"os" != "win32"} ``` None...

OK :+1: I understand where you are coming from. From an opam-repo perspective "fetching the bundled output from the internet as part of the build process" introduces an additional dependency...

Thanks! > Well if the repository is where the sources are also downloaded (github for now), I think it should be acceptable. Indeed. I suppose one could also consider including...

CI summary: - fails on build on arch, fedora-41, and fedora-42 with `Could not find the required dependency GMP (>= 6.3) in the system` which I believe is a `conf-gmp`...

I was looking over the CI failure too: - #28428 should fix the Arch failure. That PR is now merged, so if you rebase on `master` those 2 errors should...

FTR, I restarted the failing Windows workflow and now it is passing :+1: I'll let `opam-ci` complete now.

I see a `runtest` linking error for rpclib-async on riscv64: https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/2d04beee37100f8a8d89ef140421171f0eeb5625/variant/extras,riscv64-ocaml-5.4,rpclib-async.10.0.0,tests ``` #=== ERROR while compiling rpclib-async.10.0.0 ================================# # context 2.5.0 | linux/riscv64 | ocaml-base-compiler.5.4.0 | pinned(https://github.com/mirage/ocaml-rpc/releases/download/10.0.0/rpclib-10.0.0.tbz) # path ~/.opam/5.4/.opam-switch/build/rpclib-async.10.0.0...

The submitted package fails on riscv64 with a linking error `undefined reference to `rdtsc'`. From a quick search, this seems to be an x86_* instruction. Any idea of why it...

FTR, #28976 addresses the Centos errors.