https://bugzilla.suse.com/show_bug.cgi?id=1205043
https://bugzilla.suse.com/show_bug.cgi?id=1205043#c5
--- Comment #5 from Stefan Hundhammer ---
Ah, you are right about libboost 1.75: It indeed exists in the Leap 15.4 repos;
but it's separate packages, not different versions of the same package. I was
looking in the "Versions" tab (in yast2 sw_single) of the first one that I saw,
not scrolling (a lot) further down in the package list to see the libbost*1_75
packages.
So there are two different package NAMES for each of those libboost packages:
- One with libboost_*1_66_0
- One with libboost_*1_75_0
Accordingly, there are also a packages libboost_headers1*-devel for both:
- libboost_headers1_66_0-devel
- libboost_headers1_75_0-devel
and the latter conflicts with libboost_headers-devel < 1.75.0.
(See also the "Dependencies" tab in yast2 sw_single)
libpoppler-devel requires libboost_headers-devel >= 1.58.
But when I look at what those libboost_headers*-devel packages provide, it's:
- libboost_headers1_66_0-devel provides
- boost-devel = 1.66.0
- libboost_headers-devel = 1.66.0
- libboost_headers1_66_0-devel = 1.66.0
- libboost_headers1_66_0-devel(x86-64) = 1.66.0
- libboost_headers1_75_0-devel provides
- libboost_headers-devel-impl = 1.75.0
- libboost_headers1_75_0-devel = 1.75.0
- libboost_headers1_75_0-devel(x86-64) = 1.75.0
What 1.75 does NOT provide, though, is libboost_headers-devel (also not
boost-devel); which is what libpoppler requires, though. And AFAICS this is
exactly the problem.
So AFAICS libboost is missing a "provides" (or two?) in its .spec file;
otherwise client packages (which are using libboost) don't have a realistic
chance of requiring any ">= version" of libboost without nailing down the exact
version with no chance of future upward compatibility.
I'd say this is a bug in the libboost packages. Let me find out who the
maintainer of that is.
--
You are receiving this mail because:
You are on the CC list for the bug.