[Pulp-dev] pulp_rpm and current backwards-compatibility problems

[Daniel Alley]

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

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.



On Tue, May 11, 2021 at 2:23 PM Grant Gainey <ggainey at redhat.com> wrote:

> On Tue, May 11, 2021 at 1:36 PM Grant Gainey <ggainey at redhat.com> wrote:
>
>>
>> I'm going to submit a PR to get pulp_rpm's CI unbroken, that has to
>> happen before we do anything else. THEN I will respond to final
>> review-comments on PR 1984. Once that passes, THEN we can talk about what
>> happens next. (That PR, for example, is affected by the proposed reverts,
>> because its migration is currently built on-top-of the one(s) being
>> reverted and will need to be renamed. So we/I probably don't want to merge
>> it, until post-revert, and an update to match the new State Of The World at
>> that point.)
>>
>> Anyway, first things first...
>>
>
> Update: no, I'm not. Marking pulp_rpm as "requires pulpcore/3.12" fails to
> build. Because core-3.12 depends on django~=2.2.20, which pulls in 2.2.21,
> which is the Broken Django, and Everything Is Sad. (Mostly me, to be honest)
>
> Right this second, we can't build against core-master, and we can't build
> against anything other than -master because of the Django Problem. PR#1985
> <https://github.com/pulp/pulp_rpm/pull/1985> is waiting while I think
> about how to make progress.
>
> G
> --
> Grant Gainey
> Principal Software Engineer, Red Hat System Management Engineering
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210511/14f08b42/attachment.htm>