Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1598524 - glibc32 Build Adjustments
Summary: glibc32 Build Adjustments
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Weimer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F35Changes
TreeView+ depends on / blocked
 
Reported: 2018-07-05 17:55 UTC by Ben Cotton
Modified: 2021-02-16 16:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ben Cotton 2018-07-05 17:55:13 UTC 
This is a tracking bug for Change: glibc 32 Build Adjustments
For more details, see: https://fedoraproject.org/wiki/Changes/glibc32_Build_Adjustments

The glibc32 package is a special package used by gcc and a few other packages to work around the lack of RPM multilib repository support in Koji. It is difficult to maintain, and the current approach raises questions regarding (L)GPL compliance.
Comment 1 Jan Kurik 2018-08-14 11:05:34 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
Comment 2 Ben Cotton 2018-08-14 13:12:53 UTC 
According to the Fedora 29 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 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 bcotton.

[1] https://fedoraproject.org/wiki/Releases/29/Schedule
Comment 3 Florian Weimer 2018-08-14 14:12:02 UTC 
We have to reschedule this to Fedora 30.  Fedora releng did not implement their part so far.
Comment 4 Ben Cotton 2019-02-19 17:12:16 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.
Comment 5 Ben Cotton 2019-03-05 21:49:58 UTC 
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.
Comment 6 Ben Cotton 2019-03-11 15:47:45 UTC 
Deferred to F31 by FESCo
Comment 7 Florian Weimer 2019-04-09 07:17:26 UTC 
We are still investigating the best way to deal with the glibc32 situation.  It may be possible to remove the package altogether.
Comment 8 Ben Cotton 2019-08-13 16:49:37 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 9 Ben Cotton 2019-08-14 17:56:13 UTC 
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.
Comment 10 Florian Weimer 2019-08-14 18:23:21 UTC 
We will likely have to move out this work again.
Comment 11 Ben Cotton 2020-02-11 15:49:18 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 12 Ben Cotton 2020-02-28 15:36:04 UTC 
I don't see any activity on this for F32. Should I defer to F33 or close it and have you resubmit when ready?
Comment 13 Florian Weimer 2020-02-28 16:18:22 UTC 
I will try to get this done for Fedora 33. An odd-numbered release is a much better fit anyway because there's no GCC rebase, so integrating this change will be easier.
Comment 14 Ben Cotton 2020-02-28 16:22:44 UTC 
Sounds good, thank you
Comment 15 Florian Weimer 2020-07-24 13:39:26 UTC 
This change will not make it into Fedora 33.
Comment 16 Ben Cotton 2020-07-24 15:28:23 UTC 
Do you want to try again for F34 or should I close the tracker and let you resubmit later when you're ready?
Comment 17 Florian Weimer 2020-07-24 15:32:58 UTC 
I want to try again for Fedora 34. Thanks.
Comment 18 Ben Cotton 2021-02-10 21:23:43 UTC 
We have reached the 'Code Complete (testable)' milestone in the Fedora 34 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 34, please set the version to rawhide.

The 100% code complete deadline is Tue 2021-02-23.
Comment 19 Ben Cotton 2021-02-16 15:52:06 UTC 
Reminder: The change complete (100% complete) deadline for Fedora 34 changes is Tuesday 23 February. At that point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA.
Comment 20 Florian Weimer 2021-02-16 16:02:37 UTC 
Sorry, this needs to be moved out again.
Note You need to log in before you can comment on or make changes to this bug.