Hi, > On 2 Jan 2025, at 10:56, Anders Montonen <anders.monto...@iki.fi> wrote: > > Hi, > >> On 2 Jan 2025, at 10:41, Song, Jiaying (CN) via lists.openembedded.org >> <Jiaying.Song.CN=windriver....@lists.openembedded.org> wrote: >> >> From: Jiaying Song <jiaying.song...@windriver.com> >> >> Change the sha256sum to the correct value due to the following error: >> WARNING: boost-native-1.86.0-r0 do_fetch: Checksum failure encountered with >> download of >> https://boostorg.jfrog.io/artifactory/main/release/1.86.0/source/boost_1_86_0.tar.bz2 >> - will attempt other sources if available >> >> Signed-off-by: Jiaying Song <jiaying.song...@windriver.com> >> --- >> meta/recipes-support/boost/boost-1.86.0.inc | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/meta/recipes-support/boost/boost-1.86.0.inc >> b/meta/recipes-support/boost/boost-1.86.0.inc >> index 2378b27575..6d6064fc7b 100644 >> --- a/meta/recipes-support/boost/boost-1.86.0.inc >> +++ b/meta/recipes-support/boost/boost-1.86.0.inc >> @@ -12,7 +12,7 @@ BOOST_MAJ = "${@"_".join(d.getVar("PV").split(".")[0:2])}" >> BOOST_P = "boost_${BOOST_VER}" >> >> SRC_URI = >> "https://boostorg.jfrog.io/artifactory/main/release/${PV}/source/${BOOST_P}.tar.bz2"; >> -SRC_URI[sha256sum] = >> "1bed88e40401b2cb7a1f76d4bab499e352fa4d0c5f31c0dbae64e24d34d7513b" >> +SRC_URI[sha256sum] = >> "79e6d3f986444e5a80afbeccdaf2d1c1cf964baa8d766d20859d653a16c39848" >> >> UPSTREAM_CHECK_URI = "http://www.boost.org/users/download/"; >> UPSTREAM_CHECK_REGEX = "release/(?P<pver>.*)/source/" >> -- >> 2.34.1 > > The url > https://boostorg.jfrog.io/artifactory/main/release/1.86.0/source/boost_1_86_0.tar.bz2 > > <https://boostorg.jfrog.io/artifactory/main/release/1.86.0/source/boost_1_86_0.tar.bz2> > points to an error page. Also, in both this update and the Scarthgap 1.84.0 > update you posted, you’re updating the recipes to the same sha256sum. I’m > guessing these patches were not tested at all? I would also have expected the > reason for the changed checksum in the commit message. > > Is there a reason the Boost recipes are not using archives.boost.io > <http://archives.boost.io/>?
According to this comment, JFrog are no longer providing a mirror for Boost: https://github.com/boostorg/boost/issues/996#issuecomment-2567031602 -a
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#209259): https://lists.openembedded.org/g/openembedded-core/message/209259 Mute This Topic: https://lists.openembedded.org/mt/110386235/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
