From Fedora Project Wiki
(clarify change ownership)
(adding release notes tracker)
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Boost 1.83 upgrade =
= Boost 1.83 upgrade =


<!--
<!--
Line 19: Line 21:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF40]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 25: Line 27:
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
[[Category:SystemWideChange]]
[[Category:SystemWideChange]]
* Targeted release: [[Releases/40 | Fedora 40 ]]
* Targeted release: [[Releases/40 | Fedora Linux 40 ]]
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
Line 34: Line 36:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* devel thread: TODO
* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/CYKLJ6GQUYLRZ4DPVO4KOHW6DSDBS5F6/ Announced]
* FESCo issue: TODO
* [https://discussion.fedoraproject.org/t/f40-change-proposal-boost-1-83-upgrade-system-wide/98916 Discussion thread]
* Tracker bug: TODO
* FESCo issue: [https://pagure.io/fesco/issue/3127 #3127]
* Release notes tracker: TODO
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2258089 #2258089]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/1076 #1076]


== Detailed Description ==
== Detailed Description ==
Line 51: Line 54:
Fedora will stay relevant, as far as Boost clients are concerned.  
Fedora will stay relevant, as far as Boost clients are concerned.  


Boost 1.82/1.83 includes two new libraries:
Boost 1.83 and 1.82 do not bring any new components, but includes two new header-only libraries -
* Compat: A repository of C++11 implementations of standard components added in later C++ standards, from Peter Dimov and contributors.
* Mysql: A C++11 client for the MySQL database server, based on Boost.Asio, from Ruben Perez.  
* Mysql: A C++11 client for the MySQL database server, based on Boost.Asio, from Ruben Perez.  
* Compat: A repository of C++11 implementations of standard components added in later C++ standards, from Peter Dimov and contributors.


Boost 1.82/1.83 also includes many fixes and enhancements to existing components, including major and potentially
Boost 1.83 also includes many fixes and enhancements to existing components, including major and potentially breaking changes to
breaking changes to -
* Multi-index Containers: Serialization now uses std::size_t instead of unsigned long to save and load the size of a multi_index_container (unsigned long is smaller than std::size_t in LLP64 data models). multi_index_container serialization class version has been bumped from 3 to 4 to reflect this change.
* TODO
* Timer: Disable deprecated headers unless BOOST_TIMER_ENABLE_DEPRECATED is defined.
 
Additionally the following breaking changes were introduced in Boost 1.82 and so also affect 1.83:
* Atomic: Removed atomic<T>::storage() accessors and atomic<T>::storage_type types that were deprecated in Boost.Atomic 1.73. Users are recommended to use atomic<T>::value() and atomic<T>::value_type instead.
* Geometry: The WKT output presentation of an empty polygon is now POLYGON() to make it consistent with other geometries
* Math: Deprecated C++11 support.
* Multiprecision: Deprecated C++11 support.
* Process: Deprecated wait_for & wait_until in V1 - they will be removed in the future!


== Scope ==
== Scope ==
Line 105: Line 115:
== Contingency Plan ==
== Contingency Plan ==


* Contingency mechanism: Worst case scenario is to abandon the update and simply ship F37 with Boost 1.76, which is already in rawhide.
* Contingency mechanism: Worst case scenario is to abandon the update and simply ship F40 with Boost 1.81, 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 2020, ideally before the mass rebuild. -->
<!-- * Contingency deadline: We will know whether the change can be made once the rebuilds in the side tag are done, which will be July 2020, ideally before the mass rebuild. -->
Line 113: Line 123:


== Documentation ==
== Documentation ==
* https://www.boost.org/users/history/version_1_83_0.html
* https://www.boost.org/users/history/version_1_83_0.html (released on 11th August 2023)
* https://www.boost.org/users/history/version_1_82_0.html
* https://www.boost.org/users/history/version_1_82_0.html (released on 14th April 2023)
* https://www.boost.org/users/history/version_1_81_0.html (expected release mid December 2022)
* https://www.boost.org/users/history/version_1_81_0.html (released on 14th December 2022)
* https://www.boost.org/users/history/version_1_78_0.html (released on 8th December 2021)
* https://www.boost.org/users/history/version_1_77_0.html (released on 11 August 2021)
* https://www.boost.org/development/index.html
* https://www.boost.org/development/index.html


== Release Notes ==
== Release Notes ==
<!-- TODO -->
<!-- TODO -->

Latest revision as of 20:04, 28 February 2024

Boost 1.83 upgrade

Summary

This change brings Boost 1.83 to Fedora. This will mean Fedora ships with a recent upstream Boost release.

Owner

Current status

Detailed Description

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/F39Boost181, Changes/F37Boost178, Changes/F35Boost176, 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 40 includes Boost 1.83.

Fedora will stay relevant, as far as Boost clients are concerned.

Boost 1.83 and 1.82 do not bring any new components, but includes two new header-only libraries -

  • Compat: A repository of C++11 implementations of standard components added in later C++ standards, from Peter Dimov and contributors.
  • Mysql: A C++11 client for the MySQL database server, based on Boost.Asio, from Ruben Perez.

Boost 1.83 also includes many fixes and enhancements to existing components, including major and potentially breaking changes to

  • Multi-index Containers: Serialization now uses std::size_t instead of unsigned long to save and load the size of a multi_index_container (unsigned long is smaller than std::size_t in LLP64 data models). multi_index_container serialization class version has been bumped from 3 to 4 to reflect this change.
  • Timer: Disable deprecated headers unless BOOST_TIMER_ENABLE_DEPRECATED is defined.

Additionally the following breaking changes were introduced in Boost 1.82 and so also affect 1.83:

  • Atomic: Removed atomic<T>::storage() accessors and atomic<T>::storage_type types that were deprecated in Boost.Atomic 1.73. Users are recommended to use atomic<T>::value() and atomic<T>::value_type instead.
  • Geometry: The WKT output presentation of an empty polygon is now POLYGON() to make it consistent with other geometries
  • Math: Deprecated C++11 support.
  • Multiprecision: Deprecated C++11 support.
  • Process: Deprecated wait_for & wait_until in V1 - they will be removed in the future!

Scope

  • Proposal owners:
    • Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost)
    • Request a "f40-boost" build system tag (discussion):
    • 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)


Upgrade/compatibility impact

  • 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).


User Experience

  • 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.

Dependencies

Packages that must be rebuilt: $ dnf repoquery -s --releasever=rawhide --whatrequires libboost\* --disablerepo=* --enablerepo=fedora | sort -u

All clients: $ dnf repoquery --releasever=rawhide --archlist=src --whatrequires boost-devel --disablerepo='*' --enablerepo=fedora-source

Contingency Plan

  • Contingency mechanism: Worst case scenario is to abandon the update and simply ship F40 with Boost 1.81, which is already in rawhide.


  • Blocks release? No
  • Blocks product? None

Documentation

Release Notes