Bug 26009

Summary: Backport new rpm build macros from cauldron
Product: Mageia Reporter: Jani Välimaa <jani.valimaa>
Component: RPM PackagesAssignee: QA Team <qa-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: pterjan, sysadmin-bugs, tmb
Version: 7Keywords: advisory, validated_update
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA7-64-OK, MGA7-32-OK
Source RPM: rpm-mageia-setup-2.39-1.mga7.src.rpm CVE:
Status comment:

Description Jani Välimaa 2020-01-03 12:59:11 CET 
Current cauldron provides new rpm build macros:
%set_build_flags
%build_cflags
%build_cxxflags
%build_fflags
%build_ldflags

And for compatibility:
%__global_cflags
%__global_cxxflags
%__global_fflags
%__global_fcflags
%__global_ldflags

For compatibility with cauldron and Fedora .specs it would be a good idea to backport those macros also to mga7.
Comment 1 Jani Välimaa 2020-01-03 14:21:39 CET 
Pushed rpm-mageia-setup-2.39.2-1.mga7 to core/updates_testing for mga7.

SRPMS:
rpm-mageia-setup-2.39.2-1.mga7

RPMS:
rpm-mageia-setup-2.39.2-1.mga7
rpm-mageia-setup-build-2.39.2-1.mga7

Assignee: bugsquad => qa-bugs

Comment 2 Jani Välimaa 2020-01-03 14:47:53 CET 
New rpm macros can be evaluated with "rpm -E". If macros aren't available, evaluation returns just the macro name.

For example:
$ rpm -E %build_cflags
-O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fasynchronous-unwind-tables

$ rpm -E %__global_ldflags
 -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags
Comment 3 Thomas Backlund 2020-01-09 21:27:46 CET 
@Pascal, please add the needed rpm-setup fixes to this update, so we can flush it all out at the same time

CC: (none) => pterjan, tmb
Keywords: (none) => feedback

Comment 5 Thomas Backlund 2020-01-09 23:06:08 CET 
(In reply to Pascal Terjan from comment #4)
> Those are the 3 commits needed:
> 
> http://gitweb.mageia.org/software/rpm/rpm-setup/commit/
> ?id=ef2cb0548e7863b5bffa5358e4e0be5ac83605f9
> http://gitweb.mageia.org/software/rpm/rpm-setup/commit/
> ?id=aeac2980f8d8c8fa46858cd0a7fca842ba334ec8
> http://gitweb.mageia.org/software/rpm/rpm-setup/commit/
> ?id=f87447dbe96a7a8a0685428ae31357689da833e3

hm, those are all already in this update...

http://gitweb.mageia.org/software/rpm/rpm-setup/log/?h=distro/mga7


Ah, we probably just need to install this update on the ec2 builders then :)
Comment 6 Thomas Backlund 2020-01-09 23:15:02 CET 
dropping feedback, this update is now installed on ec2 hosts

Keywords: feedback => (none)

Thomas Backlund 2020-01-12 00:17:08 CET

Whiteboard: (none) => MGA7-64-OK, MGA7-32-OK
CC: (none) => sysadmin-bugs
Keywords: (none) => advisory, validated_update

Comment 7 Mageia Robot 2020-01-12 00:53:23 CET 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0018.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED