Description of problem: pulp-admin rpm repo create --help has section called Repository Contents Behavior I feel Repository Content Behavior (content instead of contents) is more appropriate. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/pulp/pulp/pull/1318
This PR is was closed without merging. Should this BZ move back to NEW state?
https://github.com/pulp/pulp/pull/1316 - sorry this is the link to the merged PR. This commit is in master and 2.6-dev, changing state to MODIFIED and setting target release.
fixed in pulp 2.6.0-0.2.beta
>> rpm -qa | grep pulp-server pulp-server-2.6.0-0.2.beta.el6.noarch >> pulp-admin rpm repo create --help .... Throttling --max-downloads - maximum number of downloads that will run concurrently --max-speed - maximum bandwidth used per download thread, in bytes/sec, when synchronizing the repo Repository Content Behavior --remove-missing - if "true", units that were previously in the external feed but are no longer found will be removed from the repository; defaults to false --retain-old-count - count indicating how many non-latest versions of a unit to keep in a repository ....
Moved to https://pulp.plan.io/issues/485