Bug 1074271 - prelink installs macros files to /etc/rpm
Summary: prelink installs macros files to /etc/rpm
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: prelink
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL: https://lists.fedoraproject.org/piper...
Whiteboard:
Depends On:
Blocks: 1074261
TreeView+ depends on / blocked
 
Reported: 2014-03-09 10:47 UTC by Ville Skyttä
Modified: 2015-03-04 20:27 UTC (History)
2 users (show)

Fixed In Version: prelink-0.5.0-4.fc21
Clone Of:
Environment:
Last Closed: 2015-03-04 20:27:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ville Skyttä 2014-03-09 10:47:07 UTC
The proper location for rpm macros files in rpm >= 4.11 is
%{_rpmconfigdir}/macros.d, please move them there from /etc/rpm.

If this package's specfile targets Fedora and EL >= 7 only, the
location for macro files can be simply changed from /etc/rpm to
%{_rpmconfigdir}/macros.d. If it is intended to work on EL 5 and/or 6
as well, you can define a macros dir for example as follows (all on
one line) and install the macros to %{macrosdir}:

%global macrosdir %(d=%{_rpmconfigdir}/macros.d; [ -d $d ] || d=%{_sysconfdir}/rpm; echo $d)

Looks like this has already been fixed in git, but there are no
successful package builds with the fix in Rawhide.

Comment 1 Jaroslav Reznik 2015-03-03 15:33:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Ville Skyttä 2015-03-04 20:27:32 UTC
(In reply to Ville Skyttä from comment #0)
> Looks like this has already been fixed in git, but there are no
> successful package builds with the fix in Rawhide.

I think that's good enough for this package, the fix will trickle into releases if it ever gets fixed to build.


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