Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changelog trimming can skip changes #1723

Closed
389-ds-bot opened this issue Sep 13, 2020 · 8 comments
Closed

changelog trimming can skip changes #1723

389-ds-bot opened this issue Sep 13, 2020 · 8 comments
Labels
closed: won't fix Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48392

  • Created at 2015-12-22 19:07:14 by lkrispen (@elkris)
  • Closed at 2020-05-27 16:50:35 as wontfix
  • Assigned to nobody

Changelog trimming does not trim the anchor csns. But if an anchor csn is found there are two calls to getNext entry and the change folloing an anchor csn is skipped and not trimmed

@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.4 backlog milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2016-01-15 00:57:00

Per triage meeting...

@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2017-02-11 22:55:24

Metadata Update from @nhosoi:

  • Issue set to the milestone: 1.3.6 backlog

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-05-08 22:07:19

Metadata Update from @mreynolds389:

  • 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 backlog)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-08-23 20:36:41

@elkris - was this already fixed via a different ticket?

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-08-23 20:36:42

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-08-23 20:36:48

Metadata Update from @mreynolds389:

  • Issue set to the milestone: 1.4.2 (was: 1.3.7.0)

@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2019-08-27 10:21:47

@elkris - was this already fixed via a different ticket?

don't think so, the impact is not so big, so we could either close it or give me some time to reproduce and fix - or someone else wanting to dive into replication code

@389-ds-bot
Copy link
Author

Comment from vashirov (@vashirov) at 2020-03-18 16:25:30

Metadata Update from @vashirov:

  • Issue priority set to: minor (was: normal)
  • Issue set to the milestone: 1.4 backlog (was: 1.4.2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant