Boost 1.76 upgrade
This change brings Boost 1.76 to Fedora. This will mean Fedora ships with a recent upstream Boost release.
- Name: Thomas Rodgers
- Email: email@example.com
- Targeted release: Fedora 35
- Last updated: 2021-07-14
- FESCo issue: #2637
- Tracker bug: #1982394
- Release notes tracker: #711
The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent packages. This also entails the change owner assisting maintainers of client packages in decoding cryptic boost-ese seen in output from g++.
The equivalent changes for previous releases were Changes/F34Boost175, Changes/F33Boost173, Fedora 30 Change, Fedora 29 Change, Fedora 28 Change, Fedora 27 Change, Fedora 26 Change, Fedora 25 Change, Fedora 24 Change, Fedora 23 Change and Fedora 22 Change.
Benefit to Fedora
Fedora 35 includes Boost 1.76.
Fedora will stay relevant, as far as Boost clients are concerned. Boost 1.76 does not bring any new components but includes many fixes and enhancements to existing components. Boost 1.76 also introduces some breaking changes -
- Boost.DLL : boost::dll::import was renamed to boost::dll::import_symbol to avoid collision with C++20 import keyword.
- Boost.Math : Drops C++03 support.
- Boost.Multiprecision : Explicitly requires C++11 or later.
- Proposal owners:
- Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost)
- Request a "f35-boost" build system tag (discussion): https://pagure.io/releng/issue/9474
- Build boost into that tag (take a look at the build #606493 for inspiration)
- Post a request for rebuilds to fedora-devel
- Work on rebuilding dependent packages in the tag.
- When most is done, re-tag all the packages to rawhide
- Watch fedora-devel and assist in rebuilding broken Boost clients (by fixing the client, or Boost).
- Other developers:
- Those who depend on Boost DSOs will have to rebuild their packages. Feature owners will alleviate some of this work as indicated above, and will assist those whose packages fail to build in debugging them.
- Release engineering: TODO (a check of an impact with Release Engineering is needed)
- Policies and guidelines:
- Apart from scope, this is business as usual, so no new policies, no new guidelines.
- Trademark approval: N/A (not needed for this Change)
- No manual configuration or data migration needed.
- Some impact on other packages needing code changes to rebuild. Historically this hasn't been too much of a problem and could always be resolved before deadline.
How To Test
- No special hardware is needed.
- Integration testing simply consists of installing Boost packages (
dnf install boost) on Fedora and checking that it does not break other packages (see below for a way to obtain a list of boost clients).
- Expected to remain largely the same.
- Developers building third-party software on Fedora may need to rebuild against the new Boost packages, and may need to adjust their code if the new Boost release is not source-compatible.
Packages that must be rebuilt:
$ dnf repoquery -s --releasever=rawhide --whatrequires libboost\* --disablerepo=* --enablerepo=fedora | sort -u
$ dnf repoquery --releasever=rawhide --archlist=src --whatrequires boost-devel --disablerepo='*' --enablerepo=fedora-source
- Contingency mechanism: Worst case scenario is to abandon the update and simply ship F34 with Boost 1.73, which is already in rawhide. It would also be possible to ship the 1.74.0 which would still be newer than in current Fedora releases and contains numerous fixes and improvements to existing Boost components.
- Blocks release? No
- Blocks product? None
- https://www.boost.org/users/history/version_1_76_0.html (released on 16 April 2021)
- https://www.boost.org/users/history/version_1_75_0.html (released on 11 December 2020)
- https://www.boost.org/users/history/version_1_74_0.html (released on 14 August 2020)