On Thursday 2021-08-05 09:38, Andreas Vögele wrote:
Michael Ströder writes:
On 7/31/21 1:26 PM, Philipp Wagner wrote:
Someone submitted an update to OpenLDAP 2.5. https://build.opensuse.org/request/show/909449
That someone was me.
Personally I have no objections to simply accept your request. But I'm pretty sure, someone (not me!), has to deal with the fallout. Therefore I wanted to draw some attention to your request.
This change in OpenLDAP 2.5 is scary as it affects most users who run slapd:
"Due to database format changes between OpenLDAP 2.4 and OpenLDAP 2.5 it is mandatory for existing slapd-mdb(5) databases to be exported via an OpenLDAP 2.4 slapcat prior to upgrade. They must then be reloaded via an OpenLDAP 2.5 slapadd after the binaries are updated."
Just for the record, that is from https://www.openldap.org/doc/admin25/appendix-upgrading.html Which... isn't something the user ever goes to see when doing rpm -U/zypper. It's 2021. mysql just autoupgrades its tables (did so for years). ffmpeg just reads everything under the sun, no matter the age. Both options should be ample inspiration for openldap, but I guess I'm just praying to the user choir. Perhaps I should preach 389ds instead. "Change my mind." Also: I'm running a 2.4 mdb file with 2.5, not large, but reading it with slapcat and/or an active slapd seems to work. (Only until I hit an impasse, I guess.)
I think that OpenLDAP 2.4 cannot be replaced by version 2.5. There have to be packages for both versions. At least a statically linked slapcat from version 2.4 has to be provided.
Duplicate the spec, add Conflicts. Don't worry about installing both side-by-side. That is the least amount of work. After all, you only need to slapcat the old db, then you can replace openldap (hence no concurrent presence), then un-slapcat it.