Hi, I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4 replicas all on RedHat which I would like to abandon in favor Debian which is my main platform.
My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is completely missing 389-admin package [1]. They ship cockpit-389-ds 1.4.0.21-1 which completely doesn't work on Debian. It declares that 389-ds-base isn't installed. It is installed and configured. I tried Fedora 29, there is 1.4.0.21-1.fc29 and it works... somehow. Schema editation is possible. But database management is broken, it shows two suffixes dc=example,dc=com and o=ipaca.com which are not present in 389-ds configuration dse.ldif file. And it is unable to detect defined suffix. It looks nice, but it seems that many things might not be working even on Fedora. Is it possible to manage 389-ds 1.4.x with 389-admin 1.1.46 and 389-admin-console 1.1.12-5.fc29? This is combination Fedora 29 come with. Or is it safer to stick with 389-ds 1.3.x which is shipped with RHEL 7 & Debian/Stretch? And use 389-admin & 389-console for managing them? Thanks for responses [1] https://packages.debian.org/search?keywords=389-admin&searchon=names&suite=all§ion=all -- ----------------------- Jan Tomasek aka Semik http://www.tomasek.cz/ _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
