Use achives.boost.io instead of jfrog for fetching boost #9417
Conversation
|
This pull request was exported from Phabricator. Differential Revision: D52612598 |
Summary: X-link: facebook/openzl#667 X-link: facebook/wangle#224 AIRStore's contbuild broke a few days ago with a failure to unpack the boost tarball. This is because boost's jfrog subscription expired. The recommended workaround is to use `archive.boost.io` instead. The checksums are the same. facebook/react-native#42180 Reviewed By: chadaustin Differential Revision: D52612598
ASchneidman
force-pushed
the
export-D52612598
branch
from
6b69dd5 to
1824b2d
Compare
|
This pull request was exported from Phabricator. Differential Revision: D52612598 |
|
Hi @ASchneidman! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Summary: AIRStore's contbuild broke a few days ago with a failure to unpack the boost tarball. This is because boost's jfrog subscription expired. The recommended workaround is to use
archive.boost.ioinstead. The checksums are the same. facebook/react-native#42180Reviewed By: chadaustin
Differential Revision: D52612598