[OE-core] [PATCH] boost: Fix SRC_URI checksums

Paul Eggleton paul.eggleton at linux.intel.com
Wed Nov 2 02:43:35 UTC 2016


On Tue, 01 Nov 2016 09:45:48 Khem Raj wrote:
> > On Nov 1, 2016, at 9:33 AM, Alexander Kanavin
> > <alexander.kanavin at linux.intel.com> wrote:> 
> > On 11/01/2016 06:06 PM, Khem Raj wrote:
> >>>> we should specify boost/boost/1.62.0/boost_1_62_0.tar.bz2 instead of
> >>>> boost/boost/boost_1_62_0.tar.bz2>>> 
> >>> Incorrect. That will still download a master snapshot tarball. Only if
> >>> the 'project/' is prefixed, SF will give you the release tarball.>> 
> >> if we need projects/ then it should be encoded into SOURCEFORGE_MIRROR
> >> variable in bitbake.conf. Since that required for every sf.net project.
> > 
> > Would you then also fix the remaining recipe-specific part of the URI in
> > all those recipes? I don't have the bandwidth for that right now, and
> > it's a problem that is unlikely to happen in other recipes.
>
> I wonder if same problem would not happen for other sf.net packages.
> probably we never run into it probably because it gets backed up on yp
> download mirror and then used. I am not expecting you to fix it, don't
> worry.

I think it's less likely to happen elsewhere because most projects don't 
release snapshot tarballs with the exact same name as the latest stable 
release ones. Someone really ought to explain to the boost folks why that is a 
bad idea.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



More information about the Openembedded-core mailing list