Actions
Backport #9298
closedBackport #9287 "Copy API does depsolving twice" to 3.14.z
Start date:
Due date:
% Done:
100%
Estimated time:
Triaged:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
When we took out the code that tries to 'fix' depsolving problems, we left in the loop that assumes it's happening. This means that calling /copy/ with depsolving=True does the depsolving twice, every time, before continuing.
Given the performance- and memory-characteristics of the current depsolving processing, this is...Bad.
Related issues
Updated by dalley about 3 years ago
- Copied from Issue #9287: Copy API does depsolving twice added
Updated by pulpbot about 3 years ago
- Status changed from NEW to POST
Added by dalley about 3 years ago
Updated by dalley about 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 1c10d0de100deb1ed168058b3ba6921ea48d61a3.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
On copy, depsolving was running twice. Taught it to Not Do That.
backports #9287. [nocoverage]
fixes #9298
(cherry picked from commit eb161f21a71a03a0741c48543af7b4360d7cbb79)