Bug 2161319

Summary:	gambas3: Use %_fortify_level instead of twiddling with RPM_OPT_FLAGS
Product:	[Fedora] Fedora	Reporter:	Siddhesh Poyarekar <sipoyare>
Component:	gambas3	Assignee:	Tom "spot" Callaway <spotrh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	38	CC:	spotrh
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:	2023-03-24 15:33:05 UTC	Type:	Bug
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:	2158232

Description Siddhesh Poyarekar 2023-01-16 15:23:51 UTC

Description of problem:
There is now a canonical way to disable fortification, see "Fortification level" in the build flags guide:

https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/rawhide/f/buildflags.md#source-fortification

This way, one doesn't need to mess with RPM_OPT_FLAGS anymore to do this.

Comment 1 Ben Cotton 2023-02-07 15:05:42 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 2 Siddhesh Poyarekar 2023-03-24 15:33:05 UTC

This was fixed:

commit 576b2d0ffc7bf9516756e051b4a95abd0ce0a659
Author: Tom Callaway <spot>
Date:   Wed Jan 18 17:14:51 2023 -0500

    3.18.0