Using iurt to build a rpm package that depends on lib64keyutils-devel fails when BuildRequires: pkgconfig(libkeyutils) is used in a spec file, but it works fine if keyutils-devel is used. For some reasons, using the link directory for libraries(i.e. "/%{_lib}") in the keyutils spec file messes up iurt loading/finding the rpm package. An issue with iurt/rpmbuild, maybe !?. It looks like the maintainer, for some reason, went out of the way to use /%{_lib} instead of %{_libdir}. It's been like this since Mageia 1. However, replacing "/%{_lib}" with "%{_libdir}" pleases iurt and all is good. Regards, A
Source RPM: (none) => keyutils-1.6.3-2.mga9.src.rpm
It's because pkgconfig() provides are generated from files in /usr/lib(64)/pkgconfig, and not /lib(64)/pkgconfig. I don't see any reason anymore to ship files under /lib(64), /bin, nor /sbin. I'll fix this in SVN. The fix will be in the next release.
Summary: keyutils: pkgconfig fails to load the devel keyutils pkg in an iurt build. => keyutils: devel package doesn't provide pkgconfig(libkeyutils)CC: (none) => jani.valimaaWhiteboard: (none) => MGA9TOO
Fixed in SVN. Upcoming mga9 pkg can be fixed after branching by merging the commit. https://svnweb.mageia.org/packages?view=revision&revision=1963985
Nice, I missed the sbin one. Thanks.
Thanks Jani for rapid correction. OK to close this?
Status: NEW => RESOLVEDResolution: (none) => FIXED
Looks like this bug haven't been fixed in Mageia 9, maybe got overlooked in the rush to release Mageia. The spec file mentioned by Jani in comment 2 is a fine solution and the package just needs a rebuild.
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
Please test keyutils-1.6.3-2.1.mga9 from mga9 core/updates_testing. SRPM: keyutils-1.6.3-2.1.mga10 RPMS: keyutils-1.6.3-2.1.mga10 lib(64)keyutils1-1.6.3-2.1.mga10 lib(64)keyutils-devel-1.6.3-2.1.mga10
Tested the new version and it's been properly found, installed and used in my case, I'm using it to build "stress-ng" that needs it. Thanks Jani, this runs great. Regards, A.
Thanks Jani for the work, & Aurelian for testing it OK. But Cauldron or Mageia 9 ? Comment 6 mixes the two. For M9 it will need an advisory. If A tested M9, that is good for QA OK.
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #8) > For M9 it will need an advisory. If A tested M9, that is good for QA OK. Tested Mageia 9 and Cauldron. Thanks.
Thank you for this confirmation. Needs its Advisory (adapted & checked to exist for mga9). > SRPM: > keyutils-1.6.3-2.1.mga10 > RPMS: > keyutils-1.6.3-2.1.mga10 > lib(64)keyutils1-1.6.3-2.1.mga10 > lib(64)keyutils-devel-1.6.3-2.1.mga10 > Please test keyutils-1.6.3-2.1.mga9 from mga9 core/updates_testing. It can be taken as tested OK comment 7, comment 9. Passing to QA.
CC: lewyssmith => (none)Assignee: bugsquad => qa-bugs
Advisory added to SVN: type: bugfix subject: Updated keyutils packages fix a bug src: 9: core: - keyutils-1.6.3-2.1.mga9 description: | The lib(64)keyutils-devel package did not provide pkgconfig(libkeyutils), this update fixes the issue. references: - https://bugs.mageia.org/show_bug.cgi?id=32119
CC: (none) => marja11Keywords: (none) => advisoryVersion: Cauldron => 9
MGA9-64 Plasma. No installation issues, so giving this an OK. Removing the MGA9TOO from the Whiteboard as redundant, and validating.
CC: (none) => andrewsfarm, sysadmin-bugsKeywords: (none) => validated_updateWhiteboard: MGA9TOO => MGA9-64-OK
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0140.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED