When upgrading from openldap 2.1.x to 2.2.x, there is a check whether data exists in the openldap-data directory; if this is the case, the upgrade is aborted and instructions to backup and later restore the data is printed. Unfortunately, this check doesn't work due to a typo in the ebuild. This means that there is a possibility to lose data! Reproducible: Always Steps to Reproduce: 1. upgrade from openldap 2.1.x to 2.2.x via emerge with data in openldap-data Actual Results: The upgrade is performed. Expected Results: The message "A possible old installation of OpenLDAP was detected" [...] should be printed and the upgrade aborted. Change datafiles="${datafiles} $(ls $d/*db*} 2>/dev/null)" to datafiles="${datafiles} $(ls $d/*db* 2>/dev/null)" in pkg_setup(). This typo has been introduced in the ebuild for openldap 2.2.26. In the latest ebuilds (2.2.28*), this is in line 83.
fixed now. thanks for the catch. I've only heard one case of things breaking so far (other than my own testing), and that was somebody that disabled the upgrade check themselves.
