This is a tracking bug for Change: 389_Directory_Server_3.2.0 For more details, see: https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0 Starting from 389-ds-base version 3.2.0, the directory server no longer supports the deprecated BerkeleyDB, so the LDMB database must be used. Users still using BerkeleyDB will have to migrate their data. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Dear change owner, this is a reminder that your change is required to be 100% code complete by August 26, which is the start of beta freeze. Please provide a status update on your change in the Incomplete Changes Report if you are not able to move your change to 'ON_QA' before this date. If you need to defer your change to the next Fedora release, please let me know and I will reassign this bug and the change page. Thank you kindly.
Hi @progier, apologies but this bug autoassigned to me for some reason. Can you provide a status update on how this change is going please? All F43 changes need to be 100% code complete by 26 Aug before we go into Beta freeze. If this one is good to go, feel free to change the status to ON_QA or CLOSED. Thanks!
Hi @amoloney, FYI: the code was pushed in Fedora before the mass rebuild, I see it on Rawhide so IMHO we are code complete.
FESCo discussed this today and voted: AGREED: The 389 DS Change must be split into two separate ones, one for the feature release and one for the database migration. The existing Change approval for the database migration remains approved for Fedora 43. The 3.2.0 feature release is deferred to Fedora 44. (+6, 0, 0)
I've updated https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0 to reflect that the change is backported to 3.1.3.
To split the change, I renamed the page to https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.1.3 for the fedora 43 bdb removal We still have to create a new 3.2.0 page for F44 to announce the new release