Skip to content

Package ordma.0.0.6 - #30260

Open
kit-ty-kate wants to merge 1 commit into
ocaml:masterfrom
kit-ty-kate:opam-publish-ordma.0.0.6
Open

Package ordma.0.0.6#30260
kit-ty-kate wants to merge 1 commit into
ocaml:masterfrom
kit-ty-kate:opam-publish-ordma.0.0.6

Conversation

@kit-ty-kate

Copy link
Copy Markdown
Member

ordma.0.0.6

RDMA capabilities for OCaml via rsocket



🐫 Pull-request generated by opam-publish v3.0.0

@jmid

jmid commented Jul 13, 2026

Copy link
Copy Markdown
Member

Thanks!

There are CI errors across the board which I suspect is due to the git command failing:
https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/3670238c506b9ba55e76e0956102b5a5eca57118/variant/compilers,5.5,ordma.0.0.6

#=== ERROR while compiling ordma.0.0.6 ========================================#
# context              2.5.1 | linux/x86_64 | ocaml-base-compiler.5.5.0 | pinned(https://github.com/toolslive/ordma/archive/refs/tags/0.0.6.tar.gz)
# path                 ~/.opam/5.5/.opam-switch/build/ordma.0.0.6
# command              ~/.opam/opam-init/hooks/sandbox.sh build dune build -p ordma -j 255
# exit-code            1
# env-file             ~/.opam/log/ordma-7-b54cc7.env
# output-file          ~/.opam/log/ordma-7-b54cc7.out
### output ###
# (cd _build/default && /usr/bin/sh -c 'echo let git_revision = \"$(git describe --all --long --always --dirty)\";
#                echo let major, minor, patch = $(git describe --tags --abbrev=0 | sed s/[.]/,/g);
#                echo let summary = major, minor, patch, git_revision') > _build/default/ordma_version.ml
# fatal: not a git repository (or any parent up to mount point /)
# Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
# fatal: not a git repository (or any parent up to mount point /)
# Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
# (cd _build/default && /home/opam/.opam/5.5/bin/ocamldep.opt -modules -impl ordma_version.ml) > _build/.actions/default/86d5bf655b4a40569b02d0e609f96f2f
# File "ordma_version.ml", line 4, characters 0-0:
# Error: Syntax error

bug-reports: "https://github.com/toolslive/ordma/issues"
depends: [
"ocaml" {>= "4.02.0"}
"dune" {build}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"dune" {build}
"dune"

]
available: os = "linux"
build: [
["dune" "subst"] {pinned}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
["dune" "subst"] {pinned}
["dune" "subst"] {dev}

@kit-ty-kate

Copy link
Copy Markdown
Member Author

cc @toolslive

@toolslive

Copy link
Copy Markdown

https://github.com/toolslive/ordma/blob/master/ordma.opam

I deleted release, 0.0.6 , updated the opam file, retagged and re-released.

have fun.

@kit-ty-kate

Copy link
Copy Markdown
Member Author

@toolslive the opam file wasn't a problem at all (we can simply fix the opam file in this PR here, no need to change it upstream).

The syntax error (see the first comment) is the only real problem. Your build-system seems to expect ordma to be built from git but the tarball doesn't have the git repository.

@toolslive

Copy link
Copy Markdown

The syntax error (see the first comment) is the only real problem. Your build-system seems to expect ordma to be built from git but the tarball doesn't have the git repository.

I think the culprit is this:

(rule
  (targets ordma_version.ml)
  (action
    (with-stdout-to %{targets}
      (system "echo let git_revision = \\\"$(git describe --all --long --always --dirty)\\\";
               echo let major, minor, patch = $(git describe --tags --abbrev=0 | sed s/[.]/,/g);
               echo let summary = major, minor, patch, git_revision")
    )
  )
  (mode fallback)
)

there's a version.ml file that's generated on-the-fly... but it needs to have the git executable and a git repo.
Since it came from the tarball, it won't work....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants