legacy consumer is no longer supported and cl4 changelog is no longer used. There are lot of files not used and many checks if a replica is a legacy consumer which can be removed
attachment 0001-remove-changelog4-and-legacy-consumer-code.patch
Hi Ludwig,
Are you planning to push your patch to the master branch?
If yes, please go head and do that. If not, may I set the target milestone to 1.3.6.0?
Thanks!
let's move it to 1.3.6
Metadata Update from @lkrispen: - Issue set to the milestone: 1.3.6.0
Metadata Update from @mreynolds: - Custom field component reset (from Replication - General) - Issue close_status updated to: None - Issue set to the milestone: 1.3.7.0 (was: 1.3.6.0)
Fixed via this patch: from ticket 49038
https://pagure.io/389-ds-base/issue/raw/a78634933308824df37ca19c6ad14e1ff4fff81d4e0476da45a4116e842b6395-0001-Ticket-49038-Remove-legacy-replication.patch
c8370b8..b95f5f2 master -> master
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/1779
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.