Hello Sven,

this was partly my fault when building the new openldap package. Two things happened:

1.   between versions 2.4.x and 2.6.x build mechanism changed and
   libraries libldap|lber are built now as libldap|lber.so.xxx which is
   different to old style libldap-2.4|lber-2.4.xxx
2. I was not aware of that openindiana still provides the old Sun libraries

Now the new library naming convention clashed with the existing system ldap libraries (which you noted) and also backward compatibility was broken (all the packages linked to libldap-2.4.so). The revised package version (currently tested whether it fulfills all requirements) changes back to the old naming convention to avoid the clash and provide again backward compatibility.

I'm sorry for overseeing both points and hope the revised package works as expected.

Fritz

PS: More testers are highly appreciated, to avoid this kind of issues ;-).

Am 20.02.2022 um 13:23 schrieb Sven Schmeling:
Hello,

yesterday openldap 2.6.1 was released.

This version contains among other things the following "new" files:


root@quequak:~# pkg contents -r pkg://openindiana.org/library/openldap@2.6.1,5.11-2022.0.0.0:20220219T185128Z | grep amd | grep libldap
usr/lib/amd64/libldap.so
usr/lib/amd64/libldap.so.2
usr/lib/amd64/libldap.so.2.0.200


At the moment there is openldap 2.4 installed on all of my servers.
This version hasn't the files "libldap.so*" in it.

root@quequak:~# pkg contents -r pkg://openindiana.org/library/openldap@2.4 | grep amd | grep libldapusr/lib/amd64/libldap-2.4.so
usr/lib/amd64/libldap-2.4.so.2
usr/lib/amd64/libldap-2.4.so.2.11.6
usr/lib/amd64/libldap_r-2.4.so
usr/lib/amd64/libldap_r-2.4.so.2
usr/lib/amd64/libldap_r-2.4.so.2.11.6
usr/lib/amd64/libldap_r.so


But there is also a (installed) package which contains these now conflicting "libldap.so" files:

root@quequak:~# pkg contents -r pkg://openindiana.org/system/library@0.5.11,5.11-2022.0.0.20981:20220219T020235Z | grep amd | grep libldap
usr/lib/amd64/libldap.so
usr/lib/amd64/libldap.so.5


Today i wanted to make an update of one of the server and following happened:

root@quequak:~# pkg update -r
Creating Plan (Checking for conflicting actions): \
pkg update: The requested change to the system attempts to install multiple actions
for link 'usr/lib/amd64/libldap.so' with conflicting attributes:

    1 package delivers 'link path=usr/lib/amd64/libldap.so target=libldap.so.2.0.200':

pkg://openindiana.org/library/openldap@2.6.1,5.11-2022.0.0.0:20220219T185128Z     1 package delivers 'link path=usr/lib/amd64/libldap.so target=libldap.so.5':

pkg://openindiana.org/system/library@0.5.11,5.11-2022.0.0.20981:20220219T020235Z


These packages cannot be installed together. Any non-conflicting subset
of the above packages can be installed.




root@quequak:~# ls -al /usr/lib/amd64/libldap*
lrwxrwxrwx   1 root     root          21 Aug  1  2021 /usr/lib/amd64/libldap-2.4.so -> libldap-2.4.so.2.11.6 lrwxrwxrwx   1 root     root          21 Aug  1  2021 /usr/lib/amd64/libldap-2.4.so.2 -> libldap-2.4.so.2.11.6 -r-xr-xr-x   1 root     bin       400984 May  1  2021 /usr/lib/amd64/libldap-2.4.so.2.11.6 lrwxrwxrwx   1 root     root          12 Aug  1  2021 /usr/lib/amd64/libldap.so -> libldap.so.5 -rwxr-xr-x   1 root     bin       451072 Jan 30 13:39 /usr/lib/amd64/libldap.so.5 lrwxrwxrwx   1 root     root          23 Aug  1  2021 /usr/lib/amd64/libldap_r-2.4.so -> libldap_r-2.4.so.2.11.6 lrwxrwxrwx   1 root     root          23 Aug  1  2021 /usr/lib/amd64/libldap_r-2.4.so.2 -> libldap_r-2.4.so.2.11.6 -r-xr-xr-x   1 root     bin       438024 May  1  2021 /usr/lib/amd64/libldap_r-2.4.so.2.11.6 lrwxrwxrwx   1 root     root          23 Aug  1  2021 /usr/lib/amd64/libldap_r.so -> libldap_r-2.4.so.2.11.6


Is there a way to update the server(s)?

Thanks
Sven



_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Reply via email to