[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

> > > > I have a question / concern though. I thought that we want dbscan 2 > > ldif for emergency recovery scenarios when all else has gone bad and > > assuming that id2entry is still readable. In the approach you > > described we make the assumption that the parentid index is readable > > as

[389-devel] please review: Ticket 49295 - Fix more CI tests

https://pagure.io/389-ds-base/issue/49295 https://pagure.io/389-ds-base/issue/raw/files/feca1c383cf621a2101301aff434eb7fea620222513834530f8147f671fda751-0001-Ticket-49295-Fix-CI-tests.patch ___ 389-devel mailing list --

[389-devel] please review: Ticket 49038 - Fix regression caused by legacy replication code cleanup

https://pagure.io/389-ds-base/issue/49038 https://pagure.io/389-ds-base/issue/raw/files/e95b7815ec6de03ea3dbec6bdad8b48006beeaf8224ed25c7c99aedbd14a23b4-0001-Ticket-49038-Fix-regression-from-legacy-code-cleanup.patch ___ 389-devel mailing list --

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

2017-08-17 12:27 GMT+03:00 Ludwig Krispenz : > Hi, > Ilias' proposal follows the db2ldif approach and I think it will work, > even if it might need some tweaks to handle multiple out of order oparents. > > An other option would be to follow the total update approach using the

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

2017-08-17 3:55 GMT+03:00 William Brown : > On Tue, 2017-08-15 at 22:03 +0300, Ilias Stamatis wrote: > > 2017-08-15 9:56 GMT+03:00 William Brown : > > > > > On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote: > > > > Hi everybody, > > > > > > > >

[389-devel] Please review 48067: CI test - ds_logs :: regression tests

https://pagure.io/389-ds-base/issue/48067 https://pagure.io/389-ds-base/issue/raw/files/c7e002893fb17fc71d159ba98dc209872b922d8c90455e819a57ba1501ad16cd-0001-ds_logs-tests-bugzilla-tests.patch ___ 389-devel mailing list --