Bug 2100610 - RPM Macros for Build Flags
Summary: RPM Macros for Build Flags
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom Stellard
QA Contact:
URL:
Whiteboard:
Depends On: 2184340
Blocks: F38Changes
TreeView+ depends on / blocked
 
Reported: 2022-06-23 19:26 UTC by Ben Cotton
Modified: 2023-09-18 04:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-18 14:06:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Cotton 2022-06-23 19:26:25 UTC
This is a tracking bug for Change: RPM Macros for Build Flags
For more details, see: https://fedoraproject.org/wiki/Changes/RPMMacrosForBuildFlags

Create a corresponding macro for each compiler flag in the redhat-rpm-config macro file and create "extra flag" macros to make it easier for packages to add and remove compiler flags.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Ben Cotton 2022-07-19 15:24:45 UTC
The proposal for this Change indicated a contingency deadline of "mass rebuild", which is scheduled to begin tomorrow. Is this Change ready or does it need to be deferred to F38?

Comment 2 Tom Stellard 2022-07-20 00:16:52 UTC
I submitted the pull request here: https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/208

It seems unlikely it will be merged in time.

Comment 3 Ben Cotton 2022-08-09 16:02:52 UTC
Today we reached the Code Complete (Testable) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

At this time, all F37 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F38, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 4 Ben Cotton 2022-08-10 16:45:14 UTC
Deferring to F38 since the necessary PR is still pending.

Comment 5 Ben Cotton 2023-02-07 14:27:33 UTC
Today we reached the Code Complete (Testable) milestone on the F38 schedule: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

At this time, all F38 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F39, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 6 Tom Stellard 2023-02-07 14:33:32 UTC
I'm waiting on review/merge for https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/233.

Comment 7 Ben Cotton 2023-02-07 14:41:52 UTC
Since the contingency plan lists "mass rebuild" as the contingency date, should we defer this to F39?

Comment 8 Tom Stellard 2023-02-07 14:56:04 UTC
I think "mass rebuild" contingency date is a mistake, left over from the previous version of the proposal, which was more invasive.  I think it should be safe to merge the patch still.

Comment 9 Ben Cotton 2023-02-10 14:30:38 UTC
PR is merged, setting to MODIFIED. If it is 100% code complete now, you can set this to ON_QA.

Comment 10 Ben Cotton 2023-02-21 21:59:50 UTC
Today we reached the Code Complete (100% complete) milestone on the F38 schedule: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

At this time, all F38 Changes should be 100% complete. You can indicate this by setting this tracker to the ON_QA status. If you need to defer this Change to F39 please NEEDINFO me.

Note that we are entering the Beta freeze. Additional package changes to complete this Change will need an approved blocker or freeze exception. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for more information.

Changes that have not reached the ON_QA status will be given to FESCo for evaluation of contingency plans.

Comment 11 Ben Cotton 2023-04-04 20:10:44 UTC
From the FESCo ticket, I understand this to be complete. Setting to ON_QA. If this is wrong, please let me know ASAP.
https://pagure.io/fesco/issue/2958#comment-845168

Comment 12 Red Hat Bugzilla 2023-09-18 04:40:03 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.