On 11/23/2010 05:30 PM, Jesse Keating wrote: > On 11/23/10 5:55 AM, Jan Vcelak wrote: >> Hi! >> >> Currently, the upgrade process in openldap looks like this: >> * during db4 package upgrade run db_upgrade (%triggerin and %triggerun) >> * if minor version of openldap changes (e.g. 2.3 -> 2.4), export the database, >> delete it and import it back (which is recommended by maintanence guide, as >> Panu mentioned) >> >> We didn't wanted to do the export+import during each upgrade, as it takes >> quite a long time if you have large database. But it seems that current >> process doesn't work and that doing it every time will be the safest way. >> (Maybe we can ignore epoch changes.) >> >> Thanks for suggestions. I will fix it today and push an update. >> >> Patric, thank you for reporting this. And sorry for the difficulties. > > Why was this update made on F14 in the first place? > IMO, this is the wrong question. The better questions would be - How could it happen, this package made it into updates, dispite all this QA bureaucracy is in place? Ralf -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
