Automatic update for openldap-2.6.2-1.fc36.
Changelog
* Wed May 25 2022 Simon Pichugin <spichugi@redhat.com> - 2.6.2-1
- Rebase to version 2.6.2 (#2090447)
sudo dnf upgrade --refresh --advisory=FEDORA-2022-b65d999be6Please login to add feedback.
This update has been submitted for testing by spichugi.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works. But, these upgrade instructions and how the config is checked are totally borked. Upgrade delivers this file again, which then makes the server not start.
@bojan, thanks for testing! It's actually intentional. UPGRADE_INSTRUCTIONS file is placed on any upgrade. As per upstream, any version update should be done very carefully (https://www.openldap.org/doc/admin26/maintenance.html).
Ideally, the administrator should perform the actions before the package update. But it's not always possible, so we provide the additional safety mechanism in Fedora.
No issues querying ldap
This update can be pushed to stable now if the maintainer wishes
I get the need to be careful going from below 2.6 to 2.6. But, for a patch version upgrade? Is there no other way to figure out that required conversion steps have been done and just let slapd start?
Works
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
I think it's better to check each time the package is updated. Even in the minor version, something may happen that will affect some particular user. OpenLDAP package in Fedora doesn't have any automated upgrade scripts.
But I'm open to discussion. If I'll see Bugzillas being open by users (for now, no one mentioned that besides you). I'll start a discussion in the Fedora Devel list and gather opinions. And then I'll adjust the logic accordingly.
For now, I think it's safer to follow official OpenLDAP recommendations (doing backup on each upgrade).