This is a tracking bug for Change: mpfr-4.0.0
For more details, see: https://fedoraproject.org/wiki/Changes/mpfr-4.0.0
Update the MPFR package to version 4.0.0.
On 2018-Feb-20, we have reached the Fedora 28 Change Checkpoint: Completion deadline (testable).
At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.
Incomplete and non testable Changes will be reported to FESCo for 2018-Feb-23 meeting.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
I am afraid we will have to postpone this change. The problem is that it is an API change, not only an ABI change, so the users of MPFR need to be ready for it, a rebuild is not enough. I will discuss with James Turner what to do next (I think we should release the new version under a different name which will not conflict with the old (mpfr-3.x) version.)
I agree with Pavel. Unfortunately there are both API and ABI changes that break at least a few key dependants. A notable victim is the libmpc package, on which GCC depends.
The maintainers are unresponsive.
I furthermore agree with Pavel that releasing MPFR 4.1 as a temporary separate package would alleviate this issue, and allow other packages to catch up. I will begin working on such a package if it is agreed.
*** Bug 1528781 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
According to the Fedora 29 schedule, today is the deadline for changes to be in a testable state. If your change is ready to be tested, please set the status to ON_QA. A list of incomplete changes will be sent to FESCo tomorrow for evaluation. If you know your change will not be ready for Fedora 29, you can set the version to rawhide and notify firstname.lastname@example.org.
FESCo voted to defer this to Fedora 30.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30'.
We have reached the Code Complete (100%) milestone in the Fedora 30 development cycle. At this point, all Changes should be fully code complete and ready for testing during the beta freeze. If your Change has reached this milestone, please set the status to ON_QA. If it has not, this Change will be submitted to FESCo to evaluate the contigency plan and decide if the Change will continue in the Fedora 30 cycle.
Change Owner has withdrawn the change for the time being.
Approved by FESCo as https://fedoraproject.org/wiki/Changes/mpfr-4.0.2
The builds are done and have been tagged into Rawhide.
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 30 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.