Failed to extract archive boost_1_78_0.zip

[MikhailGorobets]

Description of Issue

I am getting this error when attempting to build the project.

I have analyzed the source code of the project build script and have come to the conclusion that it is related to this issue
boostorg/boost#842

Steps to Reproduce

1. clone OpenUSD
2. pip install PySide6
3. open the "x64 Native Tools Command Prompt for VS 2022" as administrator
4. python .\build_scripts\build_usd.py --build-variant debug .\build\Debug

System Information (OS, Hardware)

Windows

[tallytalwar]

Filed as internal issue #USD-9131

[meshula]

Hi, I think it may be back now? @MikhailGorobets can you confirm?

[MikhailGorobets]

Hi, I think it may be back now? @MikhailGorobets can you confirm?

The website is up. I think in the dependency installation script, we can specify multiple sources for downloading files in case one of them is unavailable (if the situation repeats next year, KEKW).

[meshula]

Yes, let's do that if it starts to become an issue.

[Shimmen]

Hello! This issue seems to have reappeared, unfortunately, so an additional mirror in the build script probably wouldn't hurt. Boost actually keeps their own archive (e.g. https://archives.boost.io/release/1.78.0/source/boost_1_78_0.zip) which could be a good one.

FYI found that mirror on a USD fork 2ebd43f so thank you @buddly27!

[buddly27]

Ah, I'm glad you found the fork! I hesitated to open a new issue since I assume JFrog is currently working on resolving the issue with the broken links, but switching to a different mirror might be a good idea if it persists.

[sunyab]

Reopening this issue since the JFrog site is down again. From boostorg/boost#845 and comments on the boost mailing list it's unclear whether it will become available again or if we'll need to switch over to a different URL.

For folks running into this, the current workaround is to replace "https://boostorg.jfrog.io/artifactory/main" with "https://archives.boost.io" in build_usd.py.

We may commit this change to the dev and release branches, but we're keeping an eye on the boost discussions in case they decide to use a different host for distribution -- I'm not sure the boost.io site will be able to handle the load if/when they cutover.

[dgovil]

Maybe its worth having a bit of code that tries the frog link and then falls back to the boost archives if frog fails to provide a valid zip? I assume the boost server folks would appreciate keeping the loads low.

[sunyab]

The JFrog link is working again and per the boost mailing list it sounds it should continue to do so at least until the end of the year. I've filed a task internally to add backup download sites for boost to try to shield us from this in the future.