Nick Milas wrote:

On 21/8/2013 11:48 πμ, Clément OUDOT wrote:

...

LTB project RPMs for OpenLDAP 2.4.36 are available: http://tools.ltb-project.org/news/40

I also created a yum repository to ease the installation: http://ltb-project.org/wiki/documentation/openldap-rpm#yum_repository

Thanks Clement for your effort. It surely helps the community!

Thanks to OpenLDAP project for another fine release as well.

A question: If I remember right, upgrading 2.4.34 --> 2.4.35 with mdb backend, required a rebuild of the db.

It required a rebuild of the dn2id index, accomplished by running slapindex. Not a rebuild of the entire DB.

If upgrading 2.4.35 --> 2.4.36, is there any such requirement?

No.

I assume that upgrading from any version <= 2.4.34 to 2.4.36 with mdb backend will require a rebuild of the db. Right?

Probably. slapd prints a message to this effect if it is needed.

On 21/8/2013 4:33 μμ, Howard Chu wrote:

slapd prints a message to this effect if it is needed.

Hmm. That would probably be too late... The administrator should know beforehand to plan upgrade(s). Is there a way to know beforehand?

Thanks, Nick

On 21/8/2013 9:40 μμ, Quanah Gibson-Mount wrote:

You mean http://www.openldap.org/lists/openldap-announce/201303/msg00000.html?

Exactly! I think it is important to include the notice in the change log: http://www.openldap.org/software/release/changes.html !

These announcements are not received by everyone (unless one is a member of the announcements mailing list), and it is not intuitive to be obliged to go through the announcements mailing list archives to find such important info! The change log is usually the central point of reference for admins when planning upgrades. IMHO, any and all notices of this type should be included therein. Even more so since the admin guide does not include these notices either!

Thanks and best regards! Nick