You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
70.85 downloading from https://boostorg.jfrog.io/artifactory/main/release/1.84.0/source/boost_1_84_0.tar.gz ...
72.93 checking boost_1_84_0.tar.gz...
72.95 shasum: WARNING: 1 computed checksum did NOT match
72.95 boost_1_84_0.tar.gz: FAILED
------
3 warnings found (use docker --debug to expand):
- FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 4)
- FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 19)
- FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 21)
Dockerfile:17
--------------------
15 | FROM base AS builderlinux
16 | #wally absolutely wants a running python -- it doesn't really matter the version here
17 | >>> RUN source /opt/python/default/bin/activate && ./tools/builddeps.sh --clang --prefix /prebuild/clang
18 |
19 | FROM rust:1.71-bullseye as builderrust
--------------------
ERROR: failed to solve: process "/bin/sh -c source /opt/python/default/bin/activate && ./tools/builddeps.sh --clang --prefix /prebuild/clang" did not complete successfully: exit code: 1
The current bash script that downloads dependencies downloads Boost 1.84.0 from https://boostorg.jfrog.io/artifactory/main/release/1.84.0/source/boost_1_84_0.tar.gz, which redirects to https://landing.jfrog.com/reactivate-server/boostorg. The correct file is then not downloaded, and so build fails. See an example below of a Docker image build.
Boost 1.84.0 is now hosted on https://archives.boost.io/release/1.84.0/source/boost_1_84_0.tar.gz, and so the builddeps.sh file should be updated to refer to this new URL.
The text was updated successfully, but these errors were encountered: