On 3/10/22 20:53, Marshall Clow via Boost wrote:
On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost
wrote: On 3/10/22 18:27, Marshall Clow via Boost wrote:
are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>
The SHA256 checksums are as follows:
8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I'm trying to download the source package now, and the download speed is terrible, ~30-60 KB/s. Is this expected?
That’s not what I’m seeing. I’m getting > 1 MB/sec
Possibly, some regional restrictions on JFrog side? I'm not seeing bandwidth issues on other sites, including GitHub, which I assume is US based. BTW, building with gcc 11.2 in C++17 mode on Kubuntu 21.10 succeeds. There are quite a few warnings about auto_ptr being deprecated, and also some suspicious warnings about freeing non-heap-allocated objects in Boost.Wave: https://github.com/boostorg/wave/issues/159