boost monthly download limits

boost monthly download limits

[geissonator]

Greetings,

Recently, the OpenBMC project started to hit
https://github.com/boostorg/boost/issues/299#issuecomment-593064251. Basically
the site that hosts the boost packages has a monthly download limit and once
hit, starts to fail.

There was a commit last year,
https://github.com/openembedded/openembedded-core/commit/810aded01fc2ae2c27c2573135c20947453e50c6
which moved from using sourceforge to dl.bintray.com. I don't see a reason in
the commit message but I suspect it was because sourceforge for some reason did
not mirror 1.71.0. They have 1.70.0 and 1.72.0 but not 1.71.0. I opened
https://sourceforge.net/p/boost/discussion/23622/thread/4fe1cce13b/?limit=25#7d3e
to try and understand why this was.

Given the download limitations of dl.bintray.com, does it make sense to try
and move back to sourceforge? Someone also had recommended we just grab
from github (i.e. https://github.com/boostorg/boost/archive/boost-1.71.0.tar.gz)

This issue will reset on the first of the month but could come back and bite
us again in the future. Anyone else hit this or looking into it?

Andrew

Re: [yocto] boost monthly download limits

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

I wouldn't be super concerned about that, as Yocto servers carry copies of
oe-core tarballs, and there is a fallback for that scenario. If it does
occur, we should explore alternatives, but there's no need to panic.

Alex

On Tue, 31 Mar 2020 at 21:07, Andrew Geissler <geissonator@gmail.com> wrote:

> Greetings,
>
> Recently, the OpenBMC project started to hit
> https://github.com/boostorg/boost/issues/299#issuecomment-593064251.
> Basically
> the site that hosts the boost packages has a monthly download limit and
> once
> hit, starts to fail.
>
> There was a commit last year,
>
> https://github.com/openembedded/openembedded-core/commit/810aded01fc2ae2c27c2573135c20947453e50c6
> which moved from using sourceforge to dl.bintray.com. I don't see a
> reason in
> the commit message but I suspect it was because sourceforge for some
> reason did
> not mirror 1.71.0. They have 1.70.0 and 1.72.0 but not 1.71.0. I opened
>
> https://sourceforge.net/p/boost/discussion/23622/thread/4fe1cce13b/?limit=25#7d3e
> to try and understand why this was.
>
> Given the download limitations of dl.bintray.com, does it make sense to
> try
> and move back to sourceforge? Someone also had recommended we just grab
> from github (i.e.
> https://github.com/boostorg/boost/archive/boost-1.71.0.tar.gz)
>
> This issue will reset on the first of the month but could come back and
> bite
> us again in the future. Anyone else hit this or looking into it?
>
> Andrew
>

[-- Attachment #2: Type: text/html, Size: 2476 bytes --]

Re: [yocto] boost monthly download limits

[Yann Dirson]

[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]

That may be not a problem to us, but we could still avoid to contribute to
them hitting this limitation,
I guess that was part of the original point :)

Le mar. 31 mars 2020 à 21:34, Alexander Kanavin <alex.kanavin@gmail.com> a
écrit :

> I wouldn't be super concerned about that, as Yocto servers carry copies of
> oe-core tarballs, and there is a fallback for that scenario. If it does
> occur, we should explore alternatives, but there's no need to panic.
>
> Alex
>
> On Tue, 31 Mar 2020 at 21:07, Andrew Geissler <geissonator@gmail.com>
> wrote:
>
>> Greetings,
>>
>> Recently, the OpenBMC project started to hit
>> https://github.com/boostorg/boost/issues/299#issuecomment-593064251.
>> Basically
>> the site that hosts the boost packages has a monthly download limit and
>> once
>> hit, starts to fail.
>>
>> There was a commit last year,
>>
>> https://github.com/openembedded/openembedded-core/commit/810aded01fc2ae2c27c2573135c20947453e50c6
>> which moved from using sourceforge to dl.bintray.com. I don't see a
>> reason in
>> the commit message but I suspect it was because sourceforge for some
>> reason did
>> not mirror 1.71.0. They have 1.70.0 and 1.72.0 but not 1.71.0. I opened
>>
>> https://sourceforge.net/p/boost/discussion/23622/thread/4fe1cce13b/?limit=25#7d3e
>> to try and understand why this was.
>>
>> Given the download limitations of dl.bintray.com, does it make sense to
>> try
>> and move back to sourceforge? Someone also had recommended we just grab
>> from github (i.e.
>> https://github.com/boostorg/boost/archive/boost-1.71.0.tar.gz)
>>
>> This issue will reset on the first of the month but could come back and
>> bite
>> us again in the future. Anyone else hit this or looking into it?
>>
>> Andrew
>>
> 
>


-- 
Yann Dirson <yann@blade-group.com>
Blade / Shadow -- http://shadow.tech

[-- Attachment #2: Type: text/html, Size: 3310 bytes --]

Re: [yocto] boost monthly download limits

[Ross Burton]

On Tue, 31 Mar 2020 at 20:07, Andrew Geissler <geissonator@gmail.com> wrote:
> Given the download limitations of dl.bintray.com, does it make sense to try
> and move back to sourceforge? Someone also had recommended we just grab
> from github (i.e. https://github.com/boostorg/boost/archive/boost-1.71.0.tar.gz)

That's a dynamically generated tarball that can't be relied upon, so
isn't an option.  As there's a known limitation with bintray.com I see
no reason not to move back to SF.

Patches welcome!

Ross