Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #9442

closed

Deprecation status isn't synced correctly when retain_repo_versions=1

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

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
fao89
Sprint/Milestone:
0.10.1
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 106
Quarter:

Description

If a repo with deprecated collections sync from a remote without deprecations, the repo will keep its deprecations regardless the new remote

Actions
Copy link
 #1

Updated by fao89 about 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89
Actions
Copy link
 #2

Updated by pulpbot about 3 years ago

  • Status changed from ASSIGNED to POST

Added by Fabricio Aguiar about 3 years ago

Revision a05122a9 | View on GitHub

Ensure deprecation status is in sync with the remote

closes #9442

Actions
Copy link
 #3

Updated by Anonymous about 3 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #4

Updated by rchan about 3 years ago

  • Sprint set to Sprint 106

Added by Fabricio Aguiar about 3 years ago

Revision 0aa22b13 | View on GitHub

Ensure deprecation status is in sync with the remote

closes #9442

(cherry picked from commit a05122a993845ca41c687c9a7e80967cb098249d)

Actions
Copy link
 #6

Updated by fao89 about 3 years ago

  • Sprint/Milestone set to 0.10.1
Actions
Copy link
 #7

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF