Boost 1.70 upgrade
This change brings Boost 1.70 to Fedora. This will mean Fedora ships with a recent upstream Boost release.
- Name: Jonathan Wakely
- Email: email@example.com
- Targeted release: Fedora 31
- Last updated: 2019-07-24
- Tracker bug: #1732115
- Release notes tracker: #362
The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of all dependent packages. This has also always entailed yours truly assisting maintainers of client packages in decoding cryptic boost-ese seen in output from g++. Such care is to be expected this time around as well.
The equivalent changes for previous releases were 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 30 includes Boost 1.69, but the latest upstream release, Boost 1.70, was released on April 12th, 2019.
Fedora will stay relevant, as far as Boost clients are concerned. Boost 1.70 brings two new components:
- Boost.Outcome, A set of tools for reporting and handling function failures in contexts where directly using C++ exception handling is unsuitable, from Niall Douglas.
- Boost.Histogram, Fast and extensible multi-dimensional histograms with convenient interface for C++14, from Hans Dembinski.
- Proposal owners:
- Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost)
- Request a "f31-boost" build system tag (discussion): https://pagure.io/releng/issue/8061
- 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:  (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 impact on system upgrade (no removed subpackages this time).
- No manual configuration or data migration needed.
- Some impact on other packages needing code changes to rebuild. Historically this hasn't been too big 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 F31 with Boost 1.69, which is already in rawhide.
- Contingency deadline: We will know whether the change can be made once the rebuilds in the side tag are done, which will be July 2019, ideally before the mass rebuild.
- Blocks release? No
- Blocks product? None
- https://www.boost.org/users/history/version_1_70_0.html (released on 12 April 2019)
Boost has been upgraded to version 1.70. Apart from a number of bug fixes and improvements to existing libraries, compared to Fedora 30, this brings: