Project

Profile

Help

Backport #9298

closed

Backport #9287 "Copy API does depsolving twice" to 3.14.z

Added by dalley about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
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

Copied from RPM Support - Issue #9287: Copy API does depsolving twiceCLOSED - CURRENTRELEASEggaineyActions
Actions #1

Updated by dalley about 3 years ago

  • Copied from Issue #9287: Copy API does depsolving twice added
Actions #2

Updated by pulpbot about 3 years ago

  • Status changed from NEW to POST

Added by dalley about 3 years ago

Revision 1c10d0de | View on GitHub

On copy, depsolving was running twice. Taught it to Not Do That.

backports #9287. [nocoverage]

fixes #9298

(cherry picked from commit eb161f21a71a03a0741c48543af7b4360d7cbb79)

Actions #3

Updated by dalley about 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #4

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF