On Sun, Oct 04, 2020 at 09:56:33AM +0200, Frantisek Zatloukal wrote:
I've recently begun maintaining celery stack in Fedora and Fedora EPEL.
I am in process of enabling python 3 builds of celery for EPEL 7, testing
copr (in working state with at least redis backend) is available here for
I am also planning to update all parts of celery to the latest minor
versions while I am making packaging changes. python-(vine, amqp, celery)
are all fine with only tiny changes there, however, python-kombu is a
little bit more complicated.
Current kombu version in EPEL 7 is borked  and removed by the upstream
from pypi . Long story short, they've accidentally released master
branch as kombu-4.2.2 in the past and that bad release is part of EPEL 7. I
can leave it as it is, or move to a proper, kombu 4.3 release.
From what I understand, 3rd party applications/scripts/whatever should be
using celery and not kombu directly. Current celery version present in
EPEL 7 works just fine with kombu 4.3 , I did some testing and haven't
hit any issues , it doesn't seem 3rd party applications using celery would
break/need any changes for newer kombu.
What are your opinions about this?
How big are the changes between 4.2.2 and 4.3?
ie, if someone is using 4.2.2 and you update epel7, how much will they
need to adjust?
I would lean toward doing the upgrade, but good to know what affect it
might have, and if it's going to require people to make changes,
announce in advance and leave in testing extra long.