From Fedora Project Wiki
(Add RN tracker)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= mpfr-4.0.0 <!-- The name of your change proposal --> =
+
= mpfr-4.0.2 <!-- The name of your change proposal --> =
  
 
== Summary ==
 
== Summary ==
Update the MPFR package to version 4.0.0.
+
Update the Multiple Precision Floating-Point Reliable Library (MPFR) package to version 4.0.2.
  
 
== Owner ==
 
== Owner ==
 
* Name: [[User:jamesturner246| James Paul Turner]]
 
* Name: [[User:jamesturner246| James Paul Turner]]
 
* Email: jamesturner246@fedoraproject.org
 
* Email: jamesturner246@fedoraproject.org
 +
* Name: [[User:jjames| Jerry James]]
 +
* Email: loganjerry@gmail.com
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
Line 17: Line 19:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/28 | Fedora 28 ]]  
+
* Targeted release: [[Releases/32 | Fedora 32 ]]
 
* 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 28: Line 30:
 
-->
 
-->
 
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1537252 #1537252]
 
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1537252 #1537252]
 +
* Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/402 #402]
  
 
== Detailed Description ==
 
== Detailed Description ==
The purpose of this change is to update the Fedora MPFR package to the latest version (4.0.0), released on the 25th December 2017.  Due to a soname bump, this change will rebuild all packages that depend on MPFR.
+
The purpose of this change is to update the Fedora MPFR package to the latest version (4.0.2), released on the 31st January 2019.  Due to a soname bump, this change will rebuild all packages that depend on MPFR.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
The MPFR team have released many optimisations, bugfixes and features since the current version (3.1.5), released back on the 27th September 2016. This change will allow several important Fedora packages, including the GCC, to take advantage of this.
+
The MPFR team have released many optimisations, bugfixes and features since the current version (3.1.6), released back on the 7th September 2017. This change will allow several important Fedora packages, including the GCC, to take advantage of this.
  
Refer to http://www.mpfr.org/mpfr-4.0.0/#changes for the complete list of changes.
+
Refer to http://www.mpfr.org/mpfr-4.0.0/#changes, http://www.mpfr.org/mpfr-4.0.1/#changes, and http://www.mpfr.org/mpfr-4.0.2/#changes for the complete list of changes.
  
 
== Scope ==
 
== Scope ==
Line 50: Line 53:
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
All existing user binaries built against MPFR 3.1.5 will need to be rebuilt against MPFR 4.0.0.
+
All existing user binaries built against MPFR 3.1.6 will need to be rebuilt against MPFR 4.0.2.
  
 
== How To Test ==
 
== How To Test ==
 
* No special hardware / data / etc. is needed.
 
* No special hardware / data / etc. is needed.
* To test, install mpfr-4.0.0, then rebuild and test existing user binaries.
+
* To test, install mpfr-4.0.2, then rebuild and test existing user binaries.
* Try to locally rebuild your packages with mpfr-4.0.0.
+
* Try to locally rebuild your packages with mpfr-4.0.2.
 
* Report failures and other problems to us.
 
* Report failures and other problems to us.
  
 
== User Experience ==
 
== User Experience ==
The MPFR dependent packages should behave as they did with mpfr-3.1.5.
+
The MPFR dependent packages should behave as they did with mpfr-3.1.6.
  
 
== Dependencies ==
 
== Dependencies ==
Line 65: Line 68:
  
 
== Contingency Plan ==
 
== Contingency Plan ==
*Contingency mechanism: We would like to get a special buildroot tag to be able to rebuild necessary the packages with mpfr-4.0.0. If anything goes wrong, the tag can be easily dropped, and previous version of mpfr-3.1.5 and its dependencies stays intact. The tag would be merged into F28 after everything is rebuilt.
+
*Contingency mechanism: We would like to get a special buildroot tag to be able to rebuild necessary the packages with mpfr-4.0.2. If anything goes wrong, the tag can be easily dropped, and previous version of mpfr-3.1.6 and its dependencies stays intact. The tag would be merged into F32 after everything is rebuilt.
 
* Contingency deadline: Mass Rebuild
 
* Contingency deadline: Mass Rebuild
 
* Blocks release? No
 
* Blocks release? No
Line 71: Line 74:
  
 
== Documentation ==
 
== Documentation ==
Documentation can be found upstream at http://www.mpfr.org/mpfr-4.0.0.
+
Documentation can be found upstream at http://www.mpfr.org/mpfr-4.0.2.
  
 
== Release Notes ==
 
== Release Notes ==
Line 80: Line 83:
 
-->
 
-->
  
<!-- [[Category:ChangePageIncomplete]] -->
+
[[Category:ChangeAcceptedF32]]
 
<!-- 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 87: Line 90:
  
 
[[Category:SystemWideChange]]
 
[[Category:SystemWideChange]]
[[Category:ChangeAcceptedF28]]
 

Latest revision as of 21:17, 4 October 2019

mpfr-4.0.2

Summary

Update the Multiple Precision Floating-Point Reliable Library (MPFR) package to version 4.0.2.

Owner

Current status

Detailed Description

The purpose of this change is to update the Fedora MPFR package to the latest version (4.0.2), released on the 31st January 2019. Due to a soname bump, this change will rebuild all packages that depend on MPFR.

Benefit to Fedora

The MPFR team have released many optimisations, bugfixes and features since the current version (3.1.6), released back on the 7th September 2017. This change will allow several important Fedora packages, including the GCC, to take advantage of this.

Refer to http://www.mpfr.org/mpfr-4.0.0/#changes, http://www.mpfr.org/mpfr-4.0.1/#changes, and http://www.mpfr.org/mpfr-4.0.2/#changes for the complete list of changes.

Scope

  • Proposal owners:
    • Rebuild of packages that depend on MPFR
    • Minor specfile corrections and testing
  • Other developers:
    • Testing and/or minor fixes of dependant packages
  • Release engineering: #7247
    • Separate Koji tag for package rebuild will be needed.
    • List of deliverables: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

All existing user binaries built against MPFR 3.1.6 will need to be rebuilt against MPFR 4.0.2.

How To Test

  • No special hardware / data / etc. is needed.
  • To test, install mpfr-4.0.2, then rebuild and test existing user binaries.
  • Try to locally rebuild your packages with mpfr-4.0.2.
  • Report failures and other problems to us.

User Experience

The MPFR dependent packages should behave as they did with mpfr-3.1.6.

Dependencies

   dnf repoquery --whatrequires mpfr

Contingency Plan

  • Contingency mechanism: We would like to get a special buildroot tag to be able to rebuild necessary the packages with mpfr-4.0.2. If anything goes wrong, the tag can be easily dropped, and previous version of mpfr-3.1.6 and its dependencies stays intact. The tag would be merged into F32 after everything is rebuilt.
  • Contingency deadline: Mass Rebuild
  • Blocks release? No
  • Blocks product? No

Documentation

Documentation can be found upstream at http://www.mpfr.org/mpfr-4.0.2.

Release Notes