-
Notifications
You must be signed in to change notification settings - Fork 5
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
Disentangle src_data.binaries from packages in a migration items #4
Comments
nthykier
changed the title
Disentangle src_data[BINARIES] from packages in a migration items
Disentangle src_data.binaries from packages in a migration items
Nov 12, 2016
nthykier
added a commit
that referenced
this issue
Nov 12, 2016
This commit rewrites _compute_groups to achieve the following improvements: * cruft is now handled as smooth-updatable removals * hijacking is handled sanely for single item migrations - There are some theoratical corner cases left for multi-item migrations[1] * Remove the dependency on some old assumptions (see commit 4ced8a3) [1] Assume that src-a hijacking a binary from src-b and they migrate at the same time. Closes: #4 Partly-Fixes: #792881 Signed-off-by: Niels Thykier <niels@thykier.net>
nthykier
added a commit
that referenced
this issue
Nov 12, 2016
This commit rewrites _compute_groups to achieve the following improvements: * cruft is now handled as smooth-updatable removals * hijacking is handled sanely for single item migrations - There are some theoratical corner cases left for multi-item migrations[1] * Remove the dependency on some old assumptions (see commit 4ced8a3) [1] Assume that src-a hijacking a binary from src-b and they migrate at the same time. Closes: #4 Partly-Fixes: #792881 Signed-off-by: Niels Thykier <niels@thykier.net>
nthykier
added a commit
that referenced
this issue
Nov 12, 2016
This commit rewrites _compute_groups to achieve the following improvements: * cruft is now handled as smooth-updatable removals * hijacking is handled sanely for single item migrations - There are some theoratical corner cases left for multi-item migrations[1] * Remove the dependency on some old assumptions (see commit 4ced8a3) [1] Assume that src-a hijacking a binary from src-b and they migrate at the same time. Closes: #4 Partly-Fixes: #792881 Signed-off-by: Niels Thykier <niels@thykier.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit 4ced8a3 and 2e81e55 are both issues caused by the "src_data.binaries" field being a poor over-approximation of the packages related to a given migration item. While packages in a migration item should be based on that field, it is clear they are not exactly equal to the contents of that field.
The text was updated successfully, but these errors were encountered: