Project

Profile

Help

Issue #9442

Deprecation status isn't synced correctly when retain_repo_versions=1

Added by fao89 23 days ago. Updated 11 days 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

Associated revisions

Revision a05122a9 View on GitHub
Added by Fabricio Aguiar 22 days ago

Ensure deprecation status is in sync with the remote

closes #9442

Revision 0aa22b13 View on GitHub
Added by Fabricio Aguiar 11 days ago

Ensure deprecation status is in sync with the remote

closes #9442

(cherry picked from commit a05122a993845ca41c687c9a7e80967cb098249d)

History

#1 Updated by fao89 23 days ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89

#2 Updated by pulpbot 23 days ago

  • Status changed from ASSIGNED to POST

#3 Updated by Anonymous 22 days ago

  • Status changed from POST to MODIFIED

#4 Updated by rchan 18 days ago

  • Sprint set to Sprint 106

#6 Updated by fao89 11 days ago

  • Sprint/Milestone set to 0.10.1

#7 Updated by pulpbot 11 days ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF