Do `osc buildinfo -d` and find out what pulls what: [ben@skylab:…h_network_ldap/wasm-pack]% osc buildinfo -d 15.6 | grep ldap [0] Using local file: wasm-pack.spec Using local file: _service <buildinfo project="home:ojkastl_buildservice:Branch_network_ldap" repository="15.6" package="wasm-pack" downloadurl="https://download.opensuse.org/repositories"> <error>unresolvable: nothing provides libldap-data = 2.4.46-150600.23.21 needed by libldap-2_4-2, (got version 2.6.8-lp156.3.3)</error> added libldap-2_4-2@SUSE:SLE-15-SP6:GA/pool because of libcurl4:libldap_r-2.4.so.2()(64bit) added libldap-2_4-2@SUSE:SLE-15-SP6:GA/pool because of libcurl4:liblber-2.4.so.2()(64bit) added libsasl2-3@SUSE:SLE-15-SP6:Update/pool because of libldap-2_4-2:libsasl2.so.3()(64bit) nothing provides libldap-data = 2.4.46-150600.23.21 needed by libldap-2_4-2-2.4.46-150600.23.21.x86_64@SUSE:SLE-15-SP6:GA/pool libldap-data-2.6.8-lp156.3.3.noarch@network:ldap/15.6 has version 2.6.8-lp156.3.3 - Ben Am 17.10.24 um 20:56 schrieb Johannes Kastl:
Hi Jan,
long time no read... :-)
On 17.10.24 19:00 Jan Engelhardt wrote:
On Thursday 2024-10-17 18:48, Johannes Kastl wrote:
am currently preparing packages for the LLDAP ldap server and utilities. I prepared them in a branch project derived from network:ldap.
For some reason, almost all builds for 15.5 and 15.6 are unresolvable.
nothing provides libldap-data = 2.4.46-150600.23.21 needed by libldap-2_4-2, (got version 2.6.8-lp156.3.3) Funny thing is, nothing in the package explicitely pulls in libldap-2_4-2. network:ldap/openldap2 produces
* libldap2-2.6.x.rpm which does NOT mask libldap-2_4-2-2.4.x.rpm because the name is different and we designed it with concurrent installation in mind (SLPP)
* libldap-data-2.6.x.rpm which DOES mask libldap-data-2.4.x.rpm because the name is the same
therefore, libldap-data-2.4.46.rpm from openSUSE:Leap:15.6 is not part of the resolution anymore and you get the aforelogged error.
It's an unfortunate forward incompatibility in 15.x. OK, that explains why the errors appears. But why is ldap installed at all in the build environment, if nothing pulls it in?
I currently tried this:
%if "%_repository" == "15.5" Ignore: libldap-2_4-2 %endif And? Nope.
[ 41s] + /usr/bin/cargo auditable build -j4 --offline --release [ 41s] /usr/bin/cargo: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory Hmmm, tought I could substitute 2.6 for 2.4. Did not work, too. Or I mixed up the syntax...
Kind Regards, Johannes