Bug 16886 - devel subpackage of xz missing "Provides: %{name}-devel = %{version}-%{release}"
Summary: devel subpackage of xz missing "Provides: %{name}-devel = %{version}-%{release}"
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-03 19:34 CEST by Neal Gompa
Modified: 2015-10-04 15:07 CEST (History)
1 user (show)

See Also:
Source RPM: xz-5.2.1-2.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Neal Gompa 2015-10-03 19:34:02 CEST
Description of problem:
The xz devel subpackage provides liblzma, but in most RPM-based distributions, the subpackage is called xz-devel. Package specs that try to use this name will fail to locate Mageia's devel subpackage for xz.

Suggested solution:
Add "Provides: %{name}-devel = %{version}-%{release}" to devel subpackage.

Version-Release number of selected component (if applicable):
5.2.1-2.mga6


Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2015-10-04 10:01:28 CEST
There's a lot of packaging difference between distribution.
eg: python-foo vs pyfoo (though the other distros are now coming our way b/c of python3: eg having both python-foo & python3-foo)

For devel packages, the right way to be distro agnostic is to use pkgconfig() style.
Here's, it would be "http://rpmfind.net/linux/rpm2html/search.php?query=pkgconfig%28liblzma%29"

As you can see, this is what exists everywhere:
http://rpmfind.net/linux/rpm2html/search.php?query=pkgconfig%28liblzma%29

As a side note, the naming we use is more consistent as the library really is liblzma, not libxz.
eg: Fedora's xz-libs contains liblzma.so:
http://sophie.zarb.org/rpms/40cc307310a36c312cf64d61d9e7eb56/files

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => WONTFIX

Comment 2 Neal Gompa 2015-10-04 15:07:42 CEST
Interesting, didn't know about that. Thanks.

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