Project

General

Profile

Feature #5287

As a user, I want to be able to have an upstream repo mirrored instead of additively synced

Added by Mike McCune over 8 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Repositories
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Currently if a package is removed from an upstream repository and a subsequent sync occurs those packages will still remain in the Lib.

With the addition of Package Uploads we need a way to remove packages from repositories in the Library.

Initially this would only be for custom repositories but we also need to consider policy on our Red Hat repos that ensure that they also delete packages that no longer exist on the CDN

This story has 2 main aspects:

1) handling custom content deletion
2) ensuring content synced from remote location matches the upstream (mirror style)
----
Imported from https://trello.com/c/lbspOhWF/160-13-as-a-user-i-want-to-be-able-to-remove-packages-content-from-repositories-in-the-library_

History

#1 Updated by Justin Sherrill over 8 years ago

  • Triaged set to No

Breaking off the first item into its own task:

1) handling custom content deletion

http://projects.theforeman.org/issues/5402 (packages)
http://projects.theforeman.org/issues/5403 (puppet)

#2 Updated by Justin Sherrill over 8 years ago

  • Subject changed from [13] As a user, I want to be able to remove packages(content) from repositories in the Library to [13] As a user, I want to be able to have an upstream repo mirrored instead of additively synced

#3 Updated by Eric Helms about 8 years ago

  • Subject changed from [13] As a user, I want to be able to have an upstream repo mirrored instead of additively synced to As a user, I want to be able to have an upstream repo mirrored instead of additively synced
  • Category set to 91
  • translation missing: en.field_story_points set to 13.0
  • Triaged changed from No to Yes

#4 Updated by Eric Helms over 6 years ago

  • Legacy Backlogs Release (now unused) set to 114

#5 Updated by Eric Helms over 6 years ago

  • Status changed from New to Resolved
  • Legacy Backlogs Release (now unused) changed from 114 to 86

Also available in: Atom PDF