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
Summary: | glibc32 Build Adjustments | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ben Cotton <bcotton> |
Component: | Changes Tracking | Assignee: | Florian Weimer <fweimer> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | fweimer, riehecky |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1894270 |
Description
Ben Cotton
2018-07-05 17:55:13 UTC
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[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 We have to reschedule this to Fedora 30. Fedora releng did not implement their part so far. 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. Deferred to F31 by FESCo We are still investigating the best way to deal with the glibc32 situation. It may be possible to remove the package altogether. 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. We will likely have to move out this work again. 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? 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. Sounds good, thank you This change will not make it into Fedora 33. Do you want to try again for F34 or should I close the tracker and let you resubmit later when you're ready? I want to try again for Fedora 34. Thanks. 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. 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. Sorry, this needs to be moved out again. |