389-ds-base

#51122 move CL followup (2) - complete and document cl export/import changes
Closed: wontfix by spichugi. Opened by lkrispen.

Closed: wontfix
Reopen Issue

The patch to integrate the changelog databese to the backen contains the featur to import/export the changelog along with ldif2db/db2ldif and allows a consistent export/ import eg for cert renewal.

But the implementation is incomplete, the import needs a bit work, the function stuib with comments what to do exists.
And it needs to be documented

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1843523

Issue linked to Bugzilla: Bug 1843523

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4
- Issue tagged with: Replication, lmdb

Metadata Update from @spichugi:
- Issue assigned to spichugi

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4175

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata

Replication lmdb

None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.