Project

Profile

Help

Issue #9442

closed

Deprecation status isn't synced correctly when retain_repo_versions=1

Added by fao89 about 1 year ago. Updated 12 months ago.

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

Updated by fao89 about 1 year ago

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

Updated by pulpbot about 1 year ago

  • Status changed from ASSIGNED to POST

Added by Fabricio Aguiar about 1 year ago

Revision a05122a9

Ensure deprecation status is in sync with the remote

closes #9442

Actions #3

Updated by Anonymous about 1 year ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by rchan about 1 year ago

  • Sprint set to Sprint 106

Added by Fabricio Aguiar 12 months ago

Revision 0aa22b13

Ensure deprecation status is in sync with the remote

closes #9442

(cherry picked from commit a05122a993845ca41c687c9a7e80967cb098249d)

Actions #6

Updated by fao89 12 months ago

  • Sprint/Milestone set to 0.10.1
Actions #7

Updated by pulpbot 12 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF