[Pulp-list] How does "--retain-old-count" work?

[Michael Hrivnak]

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. However, that
puts the burden on you as the user to carefully choose which content to
move where. It could be valuable if pulp offered more helpful options on
copy. Other users have expressed interest in copy operations limiting on
version, gpg signature, uniqueness of some combination of attributes, etc.
As we think about pulp 3.x, we will keep those use cases in mind.

Feedback is appreciated, so feel free to tell us more about your use cases.

Michael

On Tue, Jan 12, 2016 at 10:37 PM, Lin Yuan <yuanlinios at gmail.com> wrote:

> Hi,
>
> I am a bit puzzled with the option "--retain-old-count" from "pulp-admin
> rpm repo create --repo-id demo --retain-old-count 2" command.
>
> After I uploaded foo-1.0.0-1.el6.noarch.rpm, foo-1.1.0-1.el6.noarch.rpm,
> foo-1.2.0-1.el6.noarch.rpm,  and foo-1.3.0-1.el6.noarch.rpm to the demo
> repository and publish it, I can still see all 4 rpms from browser.
>
> So I wonder if this option only work with feed sync? Does it work with
> manual upload or copy?
>
> I am using pulp 2.7.1.
>
>
> Best Regards
> Lynn
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160113/6a7db3e6/attachment.htm>