Scott McCarty wrote:
> Randy,
> I FINALLY had a chance to file this as a user story. Holy cow, you guys
> have 200 open stories :-) So, I thought I was busy, but I have no idea how
> you guys would ever have time to implement this ;-)
Hahaha, yeah we have a lot to do for sure. Thanks for
Here is the scenario.
I synced a repo from some feed which has packages A1, B1.
Now the feed got updated to packages A2, B1.
Now when I resync I need my repo to have A2, B1 (exact mirror). The default
behaviour in pulp seems to be not touch local repo and hence it ends up having
packages A1,
Randy,
I FINALLY had a chance to file this as a user story. Holy cow, you guys
have 200 open stories :-) So, I thought I was busy, but I have no idea how you
guys would ever have time to implement this ;-)
Nick,
I added your idea of the Builder Image too :-)
[1]:
It sounds like you want to use "remove-missing", which will remove local
packages that are now missing from the remote repo.
However, if the remote feed actually now has A1, A2, and B1, but you don't
care about A1 anymore, then set retain-old-count to 0. That will cause pulp
to keep zero old
Lynn,
Thanks for asking. You are correct that this setting only works during sync.
Pulp is designed right now so that once content is in the system, it can be
copied around very quickly and cheaply. As such, we've avoided doing much
of anything during copy besides add references in the DB.
The first 2.8.0 beta is now available at it's usual location[0]. This release
contains the following packages and their dependencies:
Pulp 2.8.0 beta
RPM plugin 2.8.0 beta
Puppet plugin 2.8.0 beta
OSTree plugin version 1.1.0 beta
Python plugin version 1.0.1
Docker plugin version 2.0.0 beta
