Fedora 27 Boost 1.64 upgrade
This change brings Boost 1.64.0 to Fedora 27. This will mean F27 ships with a recent upstream Boost release.
- Name: Jonathan Wakely
- Email: email@example.com
- Release notes owner:
- Targeted release: Fedora 27
- Last updated: 2017-06-28
- Tracker bug: <will be assigned by the Wrangler>
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.
Benefit to Fedora
Fedora 26 includes Boost 1.63 but the latest upstream release, Boost 1.64, was released on Apr 19th, 2017 (the 1.65.0 release isn't scheduled until August 9th so would be too late for F27).
Fedora will stay relevant, as far as Boost clients are concerned. Boost 1.64 brings one new library:
- Boost.Process: A cross-platform library for creating and communicating with child processes.
- Proposal owners:
- Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost)
- Request a "f27-boost" build system tag (discussion): https://fedorahosted.org/rel-eng/ticket/6235 → f24-boost
- 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: #6851
- List of deliverables: All deliverables will include updated Boost packages
- Policies and guidelines:
- Apart from scope, this is business as usual, so no policies, no guidelines.
- Trademark approval: N/A (not needed for this Change)
- No impact on system upgrade.
- No manual configuration or data migration needed.
- Some impact on other packages. 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:
$ repoquery -s --releasever=rawhide --whatrequires libboost\* --disablerepo=* --enablerepo=fedora | sort -u
$ 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 F26 with Boost 1.60, which is already in rawhide. If 1.63 (or 1.64) causes too many problems for clients being rebuilt then it might be possible to use 1.62 or 1.61 instead, which would still be an improvement over F24 and F25.
- Contingency deadline: We will know whether the change can be made once the rebuilds in the side tag are done, which is likely to be some time in January 2017.
- Blocks release? No
- Blocks product? None
http://www.boost.org/users/history/version_1_64_0.html 1.64 release notes
(Incomplete) Boost has been upgraded to version 1.64. Apart from a number of bugfixes and improvements to existing libraries, this brings a new library compared to Fedora 25, Boost.Process.