This is a tracking bug for Change: New 128-bit IEEE long double ABI for IBM 64-bit POWER LE For more details, see: https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition Transition IBM 64-bit POWER LE systems to the new 128-bit IEEE long double ABI.
I believe this might solve mame not building on ppc64le.
Change has been deferred by the owner. Changing Status to NEW to reflect this.
According to the Fedora 30 schedule[1], 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 MODIFIED. If you know your change will not be ready for Fedora 30, you can set the version to rawhide and notify bcotton. For more information about this milestone, see the Changes Policy[2]. [1] https://fedoraproject.org/wiki/Releases/30/Schedule [2] https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:_Completion_deadline
This was withdrawn from F30, and moved to F31.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
We have reached the 'Code Complete (testable)' milestone in the Fedora 31 release cycle. If your Change is in a testable state, please set the status to MODIFIED. If this Change will not be ready for Fedora 31, please set the version to rawhide. The 100% code complete deadline is Tue 2019-08-27.
Moving to rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
I don't see any activity on this for F32. Should I defer to F33 or close it and have you resubmit when ready?
(In reply to Ben Cotton from comment #10) > I don't see any activity on this for F32. Should I defer to F33 or close it > and have you resubmit when ready? We should move to F33. We continue to work with IBM to get this ready.
Updated again and looking for integration into F33.
After discussion with IBM this is moved into F34.
I see you set the category to ChangePageIncomplete: https://fedoraproject.org/w/index.php?title=Changes%2FPPC64LE_Float128_Transition&type=revision&diff=577682&oldid=567130 Are you ready for me to announce it for Fedora 34, or are you still working on updating it?
(In reply to Ben Cotton from comment #14) > I see you set the category to ChangePageIncomplete: > https://fedoraproject.org/w/index. > php?title=Changes%2FPPC64LE_Float128_Transition&type=revision&diff=577682&old > id=567130 > > Are you ready for me to announce it for Fedora 34, or are you still working > on updating it? Not yet ready to announce for Fedora 34. In the next month we want to sort out some compiler changes. Lets leave it ChangePageIncomplete for now?
Branching F33 Change Tracker bugs. Today is the code complete (testable) deadline. All bugs should be at least in MODIFIED state by now to indicate they are testable.
This was moved out to F34.
Today we reached the Completion deadline (testable) milestone in the Fedora schedule. All approved changes should be in a testable state. If you change is testable, please indicate this by setting the status to MODIFIED. If you need to defer the change to Fedora 35 or withdraw the change entirely, please indicate this in a comment and NEEDINFO bcotton. The 100% code complete deadline is Tuesday 23 February. By that date, your change should be fully implemented and the tracking bug set to ON_QA. For other Fedora 34 milestones, see https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
(In reply to Ben Cotton from comment #18) > Today we reached the Completion deadline (testable) milestone in the Fedora > schedule. All approved changes should be in a testable state. If you change > is testable, please indicate this by setting the status to MODIFIED. > > If you need to defer the change to Fedora 35 or withdraw the change > entirely, please indicate this in a comment and NEEDINFO bcotton. > > The 100% code complete deadline is Tuesday 23 February. By that date, your > change should be fully implemented and the tracking bug set to ON_QA. > > For other Fedora 34 milestones, see > https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html This is not going into F34. The proposal is currently ChangePageIncomplete. We are reviewing again with IBM for F35.
Closing the tracker bug for now. Will re-open if the Change proposal is resubmitted.
Fedora 36 is performing this change.
@jaku
Sorry for the spam the first time... @jakub, this Change didn't get re-proposed for F36. Since the mass rebuild started last week, can you confirm that the necessary changes were included? If not, please update for F37.
See: [1] As a package maintainer affected by this Change, I can confirm I’ve seen its effects in F36, for better [2] and for worse [3]. [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/NPKWMTSJ2A2ABNJJEH6WTZIAEFTX6CQY/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1771031#c17 [3] https://bugzilla.redhat.com/show_bug.cgi?id=2045367#c5
(In reply to Ben Cotton from comment #23) > Sorry for the spam the first time... > > @jakub, this Change didn't get re-proposed for F36. Since the > mass rebuild started last week, can you confirm that the necessary changes > were included? If not, please update for F37. The required changes were included in F36. Ben, My apologies this was a process failure on out part for switching the default. I've updated the system-wide change request retroactively given that this switch happened.
(In reply to Carlos O'Donell from comment #25) > (In reply to Ben Cotton from comment #23) > > Sorry for the spam the first time... > > > > @jakub, this Change didn't get re-proposed for F36. Since the > > mass rebuild started last week, can you confirm that the necessary changes > > were included? If not, please update for F37. > > The required changes were included in F36. > > Ben, My apologies this was a process failure on out part for switching the > default. > > I've updated the system-wide change request retroactively given that this > switch happened. There are still several references to Fedora 34 on the change page.
(In reply to Elliott Sales de Andrade from comment #26) > (In reply to Carlos O'Donell from comment #25) > > (In reply to Ben Cotton from comment #23) > > > Sorry for the spam the first time... > > > > > > @jakub, this Change didn't get re-proposed for F36. Since the > > > mass rebuild started last week, can you confirm that the necessary changes > > > were included? If not, please update for F37. > > > > The required changes were included in F36. > > > > Ben, My apologies this was a process failure on out part for switching the > > default. > > > > I've updated the system-wide change request retroactively given that this > > switch happened. > > There are still several references to Fedora 34 on the change page. Thanks. Fixed two instances of 34 that should be 36.
F36 was released today. If this Change did not land in the release, please notify bcotton as soon as possible.