During development of a product, each sync of a repository could bring in or remove packages. For example upstream packages: a.1, b.1 sync and publish cv version 1: a.1, b.1 upstream packages: a.2, b.1 sync and publish cv version 2: a.1, a.2, b.1 upstream packages: a.3 sync and publish cv version 3: a.1, a.2, a.3, b.1 Note that on the third sync and publish, b.1 still will exist in the katello product. This means that if the removal of b.1 from the source upstream url, testing of the product against katello would still be able to resolve that dependency. The RFE is to allow an option to remove all existing packages prior to sync. With this option enabled, cv version 3 would be: a.3
Created from redmine issue http://projects.theforeman.org/issues/10277
Upstream bug component is Content Views
Upstream bug assigned to paji
Upstream bug component is Content Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/13208 has been closed ------------- Partha Aji Applied in changeset commit:katello|7de1b3ef3befe35477c6fe2750db9e30e1de3a38.
*** Bug 1231363 has been marked as a duplicate of this bug. ***
*** Bug 1308895 has been marked as a duplicate of this bug. ***
FailedQA. @Sat6.2.0-Beta pulp-server-2.8.1.3-1.el6sat.noarch Not to mess up with a repo creation I simply used two different Beta Snaps to test it. 1. Created repo and synced Snap9.3 to it. (publish CV version 1) 2. Change repo URL to point to Snap6.1 a sync it (publish CV version 2) 3. Check repository content I expected that packages that are only in snap9.3 and not in snap6.1 would be removed from the repository... but they are not To doublecheck this scenario I also involved CV publishing and the result was that both CV versions contained the same number of packages. Can you pls confirm that this above is a valid testing scenario for this RFE?
This was included with the "Mirror on Sync" policy in 6.2. Closing as CURRENTRELEASE. Please re-open if any issues are found