Octez 21.0 packages

[killian-delarue]

Packages for Octez v21.0

[raphael-proust]

Are the packages expected to run on windows? The windows CI fails but it seems to be network related or something. Idk. Still, should these packages have an available: clause with an os condition?

[raphael-proust]

octez-rust-deps fails to build:

#=== ERROR while compiling octez-rust-deps.21.0 ===============================#
# context              2.4.0~alpha1~dev | linux/x86_64 | ocaml-base-compiler.4.14.2 | pinned(https://gitlab.com/tezos/tezos/-/archive/octez-v21.0/octez-source-21.0.tar.gz)
# path                 ~/.opam/4.14/.opam-switch/build/octez-rust-deps.21.0
# command              ~/.opam/opam-init/hooks/sandbox.sh build dune build -p octez-rust-deps -j 39
# exit-code            1
# env-file             ~/.opam/log/octez-rust-deps-7-ec9a10.env
# output-file          ~/.opam/log/octez-rust-deps-7-ec9a10.out
### output ###
# File "src/rust_deps/dune", lines 12-28, characters 0-515:
# 12 | (rule
# 13 |  (targets liboctez_rust_deps.a dlloctez_rust_deps.so wasmer.h wasm.h)
# 14 |  (deps
# ....
# 26 |   (file ../../src/lib_wasm_runtime/build.rs)
# 27 |   (glob_files_rec ../../src/lib_wasm_runtime/src/**.rs))
# 28 |  (action (no-infer (bash ./build.sh))))
# (cd _build/default/src/rust_deps && /usr/bin/bash -e -u -o pipefail -c ./build.sh)
# ./build.sh: line 20: cargo: command not found

Do you need to add a dependency to conf-rust or something like that?

[mseri]

Why can't these internal libraries be moved as vendored dependency inside octez-lib? If they are internal-only there seems to be no reason to publish them

[killian-delarue]

Are the packages expected to run on windows? The windows CI fails but it seems to be network related or something. Idk. Still, should these packages have an available: clause with an os condition?

Something like in e0f42b7 ?

[raphael-proust]

Something like

Yes. Also you should probably add these constraints in the upstream project. That way it won't be an issue for the next release.

[killian-delarue]

Something like

Yes. Also you should probably add these constraints in the upstream project. That way it won't be an issue for the next release.

It will 👍🏻 Thank you for the suggestion