Request for Pulpcore 3.22 builds

Development Releases
,
1

I’d like to request that Pulpcore 3.22 get built so we can pull it into Katello 4.8.

The timeline is slightly short due to the holiday bread. Katello 4.8 is scheduled to branch in about a month. We devs would need at least a week to run all of our tests against Pulpcore 3.22 (which can happen in parallel with a pip installation.

So, the versions:

Pulpcore 3.22.latest
Pulp-rpm 3.18.latest
Pulp-container 2.14.latest
Pulp-ansible 0.16.latest
Pulp-file 1.11.latest
Pulp-python 3.8.latest
Pulp-deb 2.20.latest
Pulp-ostree 2.0.latest
Pulp-certguard 1.5.latest

2 Likes
2

Ack, I’ll start to work on it next week.

3 Likes
3

This sounds like something that is a headline feature (foreman-documentation/katello.adoc at master · theforeman/foreman-documentation · GitHub)

1 Like
4

I just wanted to check in to see how the Pulpcore 3.22 builds are going. We’ll probably need to start integrating some time next week to make it in time for branching.

5

pulp-rpm 3.19 was just released. Would it be possible to get it into the Pulpcore 3.22 builds without adding extra pain?

6

I missed this, but Index of /pulpcore/3.22 is now live, we can later do a PR to update from 3.18.10 to 3.19.

The list with all the updated packages

pulpcore==3.22.2
pulp-file==1.11.3
pulp-container==2.14.3
pulp-deb==2.20.1
pulp-rpm==3.18.10
pulp-certguard==1.5.6
pulp-ansible==0.16.0
pulp-python==3.8.0
pulpcore-client==3.22.2
pulp-rpm-client==3.18.1

7

I’ve modified my PR to add Pulp 3.22 support to our installer:

8

That fails because the GPG key is missing: https://yum.theforeman.org/pulpcore/3.22/GPG-RPM-KEY-pulpcore is a 404.