Re: [Pulp-dev] issue #3360 follow up

After meeting with @dkliban and @jortel to discuss #3360, we came up with an alternative proposal that has some small tweaks. Basically, all three parameters (add_content, remove_content, and base_version) could be used together and the parameter for the repository version would be called

Re: [Pulp-dev] pulp errata issue.

1) This email belongs on the pulp-l...@redhat.com mailing list meant for users. You are more likely to get help from other Pulp users on that list. 2) What do you mean "achieve downloading of RPMs with pulp-admin"? pulp-admin is a CLI for interacting with Pulp. pulp-admin does not download

Re: [Pulp-dev] pulp 3 PR testing with pulp-smash

Yea, it’s a bit unclear, but Pulp 3. David On Fri, Feb 23, 2018 at 10:34 AM, Robin Chan wrote: > Really basic question, but to be clear, these are changes for Pulp 2 or > Pulp 3? > > On Thu, Feb 22, 2018 at 5:40 PM, Dennis Kliban wrote: > >> We are

Re: [Pulp-dev] pulp 3 PR testing with pulp-smash

Really basic question, but to be clear, these are changes for Pulp 2 or Pulp 3? On Thu, Feb 22, 2018 at 5:40 PM, Dennis Kliban wrote: > We are currently using the Jenkins GitHub PR builder plugin to perform the > API calls at the end of the job. I don't think this plugin

Re: [Pulp-dev] pulp errata issue.

Hello Dennis- Thank you for quick response. I’m trying to understand, can I achieve downloading the rpms through using pup-admin commands(command mentioned in the below mail.) I will really happy if that works. Thanks Anand vamsi. From: Dennis Kliban [mailto:dkli...@redhat.com] Sent: