Issues with qpid-proton due to 0.35.0 release in EPEL

[ekohl]

@ehelms

• Ask maintainers to publish to EPEL a python2-qpid-proton at the right version

I’d start with this.

@ehelms

• Update (I think) gofer on EL7 to use Python 3

I also came to the conclusion that gofer is our only consumer of it. We already build it against Python 3 for EL8 so I’d expect it to work on EL7 as well. The only consumer of gofer is katello-host-tools. That only has minimal dependencies. However, it does have a lot of conditionals for various distros and versions.

@ehelms

• Build the whole stack ourselves like we do on EL8 and backport this all the places
• Try to find, build and carry a python 2 version of of qpid-proton at the right version in our repositories

We have qpid-proton in our repositories (https://github.com/theforeman/foreman-packaging/blob/rpm/develop/packages/katello/qpid-proton/qpid-proton.spec) but it’s at version 0.32.0. Using that on EL7 is probably a good recipe for conflicts. EPEL7 is also present and if they update, they’ll be newer and thus preferred.

My preference is pretty much the order you posted: first try to ask the maintainers for python-qpid-proton. It’d be the safest also for existing installations. If they don’t want to, I’d prefer change our stack to use Python 3.