https://pagure.io/389-ds-base/issue/49237 https://pagure.io/389-ds-base/issue/raw/files/e94d4e8aaa9621f96c4301ee3db12c29876c5c749205f7db7da5492fbe9622a5-0001-Ticket-49237-Drop-support-for-libdb-older-than-4.7.patch https://pagure.io/389-ds-base/issue/raw/files/c87637e957a488a0f786edb18ab3d7c15b38fec3d6895b4a18b17a325e170e16-0002-Remove-unused-parameter-from-back-ldbm-dblayer.c.patch The patches themselves remove support of old libdb (< 4.7). However there is still question about code in ldap/servers/slapd/back-ldbm/upgrade.c I haven't touched it because I have no idea which on-disk libdb formats we can assume that users have. Can we, for example, assume that all existing DS installations which will upgrade to current master branch have at least libdb 4 on-disk format and newer? If yes, the upgrade.c code can be cleaned as well. Regards, Adam -- Adam Tkac _______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
