Package: slapd Version: 2.4.40+dfsg-1 Severity: normal slapd's postinst only considers install and upgrade cases (via is_initial_configuration), handling for others is missing.
Specifically, if postinst is called with abort-upgrade because preinst failed, the upgrade path is taken. This should be mostly harmless, but could cause some confusion: if 2.4.44's preinst fails, we back up the config in /var/backups/slapd-2.4.44; and when upgrading that to some other version later, we'll do it again. This could cause confusion if, for example, an overlay or database was deleted in the meantime: it would still be in the backup folder, it would still be in the backup folder, as the new backup is only copied over top.
