Nikita Kniazev

File upstream bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114775.

> ``` > ./bootstrap.sh \ > --with-libraries=system,thread,chrono,serialization,regex``` > ``` You are asking to build Boost.Thread but you are disabling threads support with `threading=single cxxflags=-no-pthread`. It makes no sense, the error...

#19212 fixed the issue. Boost 1.85 / b2 5.0.0 also has a workaround for the cmd.exe bug.

> Apart from that, the data doesn't look usable, it contains duplicates and doesn't allow to tell similarly named packages from each other, especially it doesn't mark python modules as...

> ### Discovering upstream releases which are not yet packaged anywhere I think this is orthogonal. It would be nice to have, seeing achieved repository gives a clear signal of...

> > couldn't find a dedicated issue about that. > > There probably isn't one. I've created https://github.com/repology/repology-updater/issues/1411. > > For releases that are older (let say 2 years) a...

> Thanks Chris, I've made an upstream cmake feature request here: > > [gitlab.kitware.com/cmake/cmake/issues/18405](https://gitlab.kitware.com/cmake/cmake/issues/18405) It has been implemented in CMake 3.27 but is opt-in via policy https://cmake.org/cmake/help/latest/policy/CMP0147.html.

> @Kojoley So can we enable it when building with cmake >= 3.27? IIUC yes, I don't know where to put it though, seems to be in https://github.com/llvm/llvm-project/blob/main/cmake/Modules/CMakePolicy.cmake?

> Maybe HandleLLVMOptions.cmake? Looking at 88d7508dc479210f07abccb17f0194b66264b125 previously policies were in [llvm/CMakeLists.txt](https://github.com/llvm/llvm-project/blob/main/llvm/CMakeLists.txt) and the commit moved them to [cmake/Modules/CMakePolicy.cmake](https://github.com/llvm/llvm-project/blob/main/cmake/Modules/CMakePolicy.cmake).