Closed sophieqc closed 3 years ago
Hello,
This topic is not so easy to solve and needs investigation. If we fix it, we must fix it in RPM packages too. What's your opinion on this @coudot ?
Furthermore, I like the principle of "fail fast".
If there is no restart, we don't know if the upgrade has worked. You may be in an incoherent state.
We do this in RPM: https://github.com/ltb-project/openldap-rpm/blob/master/SPECS/openldap-ltb.spec#L578
We get the slapd running status before the upgrade and restart it only if it was running before.
Here is the behaviour expected:
For coding this behaviour, I had to revert the logic in RPM. Indeed:
Fixed with last commit 15295d9
Thank you for the quick fix.
Hello,
When debugging #52 I realized that the slapd service is automatically started even if it was stopped before
Could It be possible to make the service stay as it was before the upgrade ? It would make errors like #52 a lot easier to debug and not leave the packages in a unconfigured state.
Thanks