Bug 1651080 - EPEL meson uses Fedora _vpath_*dir macros
Summary: EPEL meson uses Fedora _vpath_*dir macros
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: meson
Version: epel7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Igor Raits
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-19 07:27 UTC by Yaakov Selkowitz
Modified: 2018-11-19 08:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-19 08:11:19 UTC
Type: Bug

Attachments (Terms of Use)

Description Yaakov Selkowitz 2018-11-19 07:27:51 UTC
Description of problem:
The %meson macro included in the EPEL meson package references %_vpath_srcdir and %_vpath_builddir, but those macros are not defined in RHEL.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  mock build a package using the %meson macro.

Actual results:
FTBFS, error message indicates that meson.build cannot be found in either directory.

Expected results:
Package builds.

Additional info:
The included macros should be changed along the lines of:

-        %{_vpath_srcdir} %{_vpath_builddir} \\\
+        . %{_target_platform} \\\

Comment 1 Igor Raits 2018-11-19 08:02:20 UTC
That is problem of RHEL, not EPEL. Actually epel-rpm-macros contain those definitions.

Comment 2 Yaakov Selkowitz 2018-11-19 08:05:45 UTC
Then EPEL meson should Requires: epel-rpm-macros.

Comment 3 Igor Raits 2018-11-19 08:11:19 UTC
No. You can provide those macros in your own foo-rpm-config.

No packages should ever require redhat-rpm-config or epel-rpm-macros. It is automatically installed in the buildroot. If you are using RHEL buildroot, you shouldn't be using EPEL repo. Or if you want to use EPEL packages, you should get epel buildroot.

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