From: Samuel DEBIONNE (samuel.debionne_at_[hidden])
Date: 2025-01-06 08:48:09
Dear all,
In the conda forge CI (that builds the boost packages), I noticed that
some jobs are failing due to a difference between the advertised and
computed sha256 checksum.
The json file at
https://archives.boost.io/release/1.87.0/source/boost_1_87_0.tar.bz2.json
has
af57be25cb4c4f4b413ed692fe378affb4352ea50fbe294a11ef548f4d527d89
While sha256sum of
https://boostorg.jfrog.io/artifactory/main/release/1.87.0/source/boost_1_87_0.tar.bz2
gives
79e6d3f986444e5a80afbeccdaf2d1c1cf964baa8d766d20859d653a16c39848
Has the archive been updated and not the sidecar json file?
Thank you,
Samuel