Description of problem:
The fc24 device-mapper-devel rpm lacks the "R: pkgconfig()":
# rpm -q --requires -p device-mapper-devel-1.02.105-1.fc24.x86_64.rpm | grep pkgconfig
..
pkgconfig
For comparison, the same for fc23:
# rpm -q --requires -p device-mapper-devel-1.02.102-2.fc23.x86_64.rpm | grep pkgconfig
...
pkgconfig
pkgconfig(libselinux)
pkgconfig(libudev)
Version-Release number of selected component (if applicable):
device-mapper-devel-1.02.105-1.fc24
Additional info:
- I am not sure who is to blame: the lvm2 packaging or rpm.
I would not want to exclude this could be a regression in rpm.
- This bug already is causing FTBFSs in other packages.
https://bugzilla.redhat.com/show_bug.cgi?id=1256862
seems to be the cause of this bug.
Proof: When removing librt/@RT_PC@ from libdm/libdevmapper.pc.in by brute force, the device-mapper-devel package receives the missing pkgconfig(...) deps.
diff --git a/lvm2.spec b/lvm2.spec
index 0fe4a89..5a47840 100644
--- a/lvm2.spec
+++ b/lvm2.spec
@@ -103,6 +103,7 @@ or more physical volumes and creating one or more logical volumes
%setup -q -n LVM2.%{version}
%patch0 -p1 -b .preferred_names
%patch1 -p1 -b .udev_no_mpath
+sed -i -e 's, @RT_PC@,,' libdm/libdevmapper.pc.in
%build
%define _default_pid_dir /run
# rpm -q --requires -p results_lvm2/2.02.128/1.fc24/device-mapper-devel-1.02.105-1.fc24.x86_64.rpm | grep pkgconfig
pkgconfig
pkgconfig(libselinux)
pkgconfig(libudev)