All of lore.kernel.org
 help / color / mirror / Atom feed
* boost monthly download limits
@ 2020-03-31 18:19 Andrew Geissler
  0 siblings, 0 replies; 2+ messages in thread
From: Andrew Geissler @ 2020-03-31 18:19 UTC (permalink / raw)
  To: yocto; +Cc: OpenBMC Maillist

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* boost monthly download limits
@ 2020-03-31 18:26 geissonator
  0 siblings, 0 replies; 2+ messages in thread
From: geissonator @ 2020-03-31 18:26 UTC (permalink / raw)
  To: yocto

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-03-31 18:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-31 18:19 boost monthly download limits Andrew Geissler
2020-03-31 18:26 geissonator

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.