Re: [Pulp-dev] signing service interface

On Tue, May 5, 2020 at 3:39 AM Quirin Pamp wrote: > Could you explain the reasoning for a 'public.key' file? > The public.key file is the file that a yum/dnf client can use to verify that the metadata in an RPM repository was signed by the signing service associated with the repository. The name

Re: [Pulp-dev] Installer project

+1 to the plan. On Tue, 5 May 2020, 19:33 Fabricio Aguiar, wrote: > Yes, it makes sense > > Best regards, > Fabricio Aguiar > Software Engineer, Pulp Project > Red Hat Brazil - Latam > +55 11 999652368 > > > On Tue, May 5, 2020 at 12:24 PM David Davis wrote: > >> Cool.

Re: [Pulp-dev] Fwd: Status of pulp-python

Hello Christoph, The Python plugin isn't abandoned, but we have not been able to maintain it due to other higher priority issues for other plugins. Our best case scenario would be to find a user or users who use the Python plugin and are interested in helping maintain this plugin. We would defini

Re: [Pulp-dev] Installer project

Yes, it makes sense Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Tue, May 5, 2020 at 12:24 PM David Davis wrote: > Cool. If we go down this path, would this plan make sense? > > 1. Create an installer project

[Pulp-dev] Migration plugin meeting notes

- In progress - [ipanova] Remotes tracking - https://github.com/pulp/pulp-2to3-migration/pull/145/ - [dalley] Progress report planning - Discussion happened on https://pulp.plan.io/issues/6590 - Dalley to file a new

Re: [Pulp-dev] Installer project

Cool. If we go down this path, would this plan make sense? 1. Create an installer project in redmine 2. Move over all issues (opened and closed) to this project that are tagged "Pulp 3 installer" 3. Remove the "Pulp 3 installer" tag David On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar wrote:

Re: [Pulp-dev] Installer project

+1 for creating a new project, Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154 Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Tue, May 5, 2020 at 11:48 AM David Davis wrote: > During tri

[Pulp-dev] Installer project

During triage today, a majority of the issues that came up were for the installer but only a handful of people could really speak to these issues. I proposed that we skip these issues during triage and let the installer team triage them. In order to do so, we'd have to create a separate project in

Re: [Pulp-dev] Fwd: Moving to travis-ci.com

Strangely, it looks like both travis-ci.com and travis-ci.org are building pulp_gem so I disabled the latter. David On Tue, May 5, 2020 at 10:16 AM Matthias Dellweg wrote: > > > -- Forwarded message - > From: Matthias Dellweg > Date: Tue, May 5, 2020 at 2:17 PM > Subject: Re:

[Pulp-dev] Fwd: Moving to travis-ci.com

-- Forwarded message - From: Matthias Dellweg Date: Tue, May 5, 2020 at 2:17 PM Subject: Re: [Pulp-dev] Moving to travis-ci.com To: Tatiana Tereshchenko Thank you! +1 for pulp_gem On Tue, May 5, 2020 at 2:15 PM Tatiana Tereshchenko wrote: > Thank you! +1 for pulp_rpm to migra

Re: [Pulp-dev] New pulpcore release (3.3.1?)

+1 for 3.3.1 Could those be included? 1. Adding TaskGroup to the plugin API https://github.com/pulp/pulpcore/pull/677 2. Adding all_task_dispatched field to indicate that no more tasks will spawn https://github.com/pulp/pulpcore/pull/682 They may sound like features/improvements however, without

Re: [Pulp-dev] fedorapeople.org fixtures

Awesome, thanks for the update. 15 minutes is more than ok as we've had gaps of days (weeks?) between updates to fedorapeople.org. David On Tue, May 5, 2020 at 9:45 AM Brian Bouterse wrote: > The osci.io team is going to try to stand up fixtures.pulproject.org by > May 15th. I'll post updates

Re: [Pulp-dev] fedorapeople.org fixtures

The osci.io team is going to try to stand up fixtures.pulproject.org by May 15th. I'll post updates here also as I continue to correspond with them. They will likely use openshift for the hosting which checks for changes every 15 minutes, so fixtures.pulproject.org would be a max of 15 minutes beh

Re: [Pulp-dev] Moving to travis-ci.com

Done. I think you'll have to update the branch protection and status check requirements once it has some builds on travis-ci.com. Also, I noticed that the cherry pick job is failing for pulp_rpm: https://travis-ci.com/github/pulp/pulp_rpm/builds/163940787 David On Tue, May 5, 2020 at 8:14 AM T

Re: [Pulp-dev] Moving to travis-ci.com

Thank you! +1 for pulp_rpm to migrate. Tanya On Tue, May 5, 2020 at 1:38 PM David Davis wrote: > I migrated over pulp_ansible, pulp-smash, and pulp-ci. I think at this > point, these are the only pulp 3 repos still on travis-ci.org: > > - pulp_rpm > - pulp_python > - pulp_gem > > If any of the

Re: [Pulp-dev] Moving to travis-ci.com

I migrated over pulp_ansible, pulp-smash, and pulp-ci. I think at this point, these are the only pulp 3 repos still on travis-ci.org: - pulp_rpm - pulp_python - pulp_gem If any of the plugins want me to migrate these over, please let me know. David On Mon, May 4, 2020 at 7:12 AM Ina Panova wr

[Pulp-dev] Fwd: Status of pulp-python

Dear all, I am currently in the process of investigating the usage of pulp for our company's repository management and think I can fulfill all the requirements except for a pypi mirror. While this is exactly what pulp-python seems to provides it has a showstopper bug: https://pulp.plan.io/issues/

Re: [Pulp-dev] signing service interface

Could you explain the reasoning for a 'public.key' file? In the case of the AptReleaseSigningService we built for pulp_deb we saw zero need for this file and consequently did not add it in. (It would not be hard to add it just to satisfy the interface, it just would not serve any useful purpos