On Thu, 2021-09-16 at 12:00 +0200, Konrad Weihmann wrote: > > On 16.09.21 11:53, Richard Purdie wrote: > > On Thu, 2021-09-16 at 11:31 +0200, Konrad Weihmann wrote: > > > Hi all, > > > > > > ERROR: expat-2.2.10-r0 do_fetch: Fetcher failure: Fetch command export > > > PSEUDO_DISABLED=1; export > > > PATH="/opt/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/opt/build/sources/poky/scripts:/opt/build/build/tmp/work/core2-64-scatest-linux/expat/2.2.10-r0/recipe-sysroot-native/usr/bin/x86_64-scatest-linux:/opt/build/build/tmp/work/core2-64-scatest-linux/expat/2.2.10-r0/recipe-sysroot/usr/bin/crossscripts:/opt/build/build/tmp/work/core2-64-scatest-linux/expat/2.2.10-r0/recipe-sysroot-native/usr/sbin:/opt/build/build/tmp/work/core2-64-scatest-linux/expat/2.2.10-r0/recipe-sysroot-native/usr/bin:/opt/build/build/tmp/work/core2-64-scatest-linux/expat/2.2.10-r0/recipe-sysroot-native/sbin:/opt/build/build/tmp/work/core2-64-scatest-linux/expat/2.2.10-r0/recipe-sysroot-native/bin:/opt/build/sources/poky/bitbake/bin:/opt/build/build/tmp/hosttools"; > > > export HOME="/github/home"; /usr/bin/env wget -t 2 -T 30 --passive-ftp > > > --no-check-certificate -P > > > /opt/build/build/tmp/work/core2-64-scatest-linux/expat/downloads > > > 'https://downloads.sourceforge.net/expat/expat-2.2.10.tar.bz2' > > > --progress=dot -v failed with exit code 8, output: > > > --2021-09-16 09:13:26-- > > > https://downloads.sourceforge.net/expat/expat-2.2.10.tar.bz2 > > > Resolving downloads.sourceforge.net (downloads.sourceforge.net)... > > > 204.68.111.105 > > > Connecting to downloads.sourceforge.net > > > (downloads.sourceforge.net)|204.68.111.105|:443... connected. > > > HTTP request sent, awaiting response... 404 Not Found > > > 2021-09-16 09:13:26 ERROR 404: Not Found. > > > > > > that one happens like every 100th attempt - and this seems to be an > > > issue of sourceforge. (I got a hunch that actually not all mirrors of SF > > > do still have the yanked version 2.2.10). > > > > I suspect you're right and this is something to do with some mirrors > > deleting > > removed files and some not. > > > > > Also the projects moved to github a while ago - are there any reasons > > > why the recipe still pulls it from sourceforge? > > > > > > If not I could spin up a patch to fetch form GH with git > > > > Tarball releases are a lot more efficient for the system. Git based recipes > > make > > the versioning less obvious and easier to break, are harder to mirror and > > thrown > > more data around causing more build IO. There are therefore pros and cons to > > tarballs vs. git urls. > > > > Sourceforge does appear to continue to store tarball releases. > > How about pulling the release tarball from github instead? > https://github.com/libexpat/libexpat/releases/download/R_2_2_10/expat-2.2.10.tar.bz2 > > should be fine IINM >
As long as those aren't dynamically built and vary their checksum, that should be ok. We may need to test/check the upstream version check urls/regex. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#156110): https://lists.openembedded.org/g/openembedded-core/message/156110 Mute This Topic: https://lists.openembedded.org/mt/85647903/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
