openviking: Add versions 0.4.17, 0.4.17.1, 0.4.18, 0.4.19, 0.4.20, 0.4.21 - #2391
Draft
riseproject-dev[bot] wants to merge 3 commits into
Draft
riseproject-dev[bot] wants to merge 3 commits into
riseproject-dev[bot] wants to merge 3 commits into
Conversation
…4.21 Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
Contributor
|
The nightly-upgrade bot bumped docs/packages/openviking.yaml to 0.4.17, 0.4.17.1, 0.4.18, 0.4.19, 0.4.20 and 0.4.21 but did not add any patches/openviking/<version>/ directory, so the "Apply patches" step's git apply failed with "No such file or directory" before the build could start. src/CMakeLists.txt still asks FindPython3 for the umbrella Development component on every one of those tags, and the 0.4.16 patch applies cleanly against each of them (verified with git apply --check), so it is copied unchanged to each new version directory.
From 0.4.18 crates/ragfs enables fred's vendored-openssl feature (pulled in by the cache feature ragfs-python always builds), so openssl-src compiles OpenSSL from source and runs its Configure script. The riscv64 manylinux image carries only perl-interpreter, and Configure died with "Can't locate FindBin.pm in @inc" (gotcha 46), failing the 0.4.20 build. Install the whole perl distribution in CIBW_BEFORE_ALL_LINUX. That OpenSSL is linked statically into the ragfs extension, so the wheel redistributes it. When Cargo.lock pins openssl-src, fetch the Apache-2.0 LICENSE.txt of the OpenSSL release it bundles (the +3.x.y build metadata of the openssl-src version) as LICENSE.openssl, and have the test command's licence check require it for those versions only.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automatically generated by the nightly
check_versions.pyrun.openviking v0.4.16 -> v0.4.17, v0.4.17.1, v0.4.18, v0.4.19, v0.4.20, v0.4.21
Every
- version:entry added todocs/packages/openviking.yamlis built by this PR's ownbuild-openviking.ymlrun; merging publishes the wheels.