Just wanted to add a comment regarding the reason for the ULN version bump below.
________________________________ From: pulp-dev-boun...@redhat.com <pulp-dev-boun...@redhat.com> on behalf of Daniel Alley <dal...@redhat.com> Sent: 11 May 2021 20:55 To: Grant Gainey <ggai...@redhat.com> Cc: Pulp-dev <pulp-dev@redhat.com> Subject: Re: [Pulp-dev] pulp_rpm and current backwards-compatibility problems These are the commits that definitely need to be reverted (in-order). We also want to check up on the signing service, either to make sure the migration plugin doesn't hit that codepath, or that we're still compatible with 3.7 even though pulpcore 3.10 introduced some changes that we had to be compatible with. But just glancing through these are the obvious ones. https://github.com/pulp/pulp_rpm/commit/d0c9badd21251e684376a6e0b0fca11c6faec208 - Matthias refactoring the auto-publish migration https://github.com/pulp/pulp_rpm/commit/fbaadaca61b5795afcfab4fcfb6ddfb52438a2da - Me adding auto-publish, and in the same commit, also the BaseDistribution change https://github.com/pulp/pulp_rpm/commit/3157ad10abf777009620ffa421b3eab45d85a5bb - Oracle ULN repo, bumped the pulpcore floor version to 3.10 from 3.7, not sure if that is 100% necessary or if it just happened The Oracle ULN repo change in pulp_rpm is dependent on this change in pulpcore: https://github.com/pulp/pulpcore/pull/1041/files Hence the raising of the floor. And then once 3.11 is out, we can re-apply those in reverse order, to get back to where we were. We'll need to fix up the migrations though. @Tanya, I know you offered to help with this, if you have any time in the morning to take a look at this, that would be excellent. I think you're the best person to figure out the answer to the signing service / migration plugin question, as well.
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-dev
