[Python-modules-team] Bug#795743: python3-celery build-depends on python3-memcache, which will be soon removed from stable

[Brian May]

Hugo Lefeuvre <hle at debian.org> writes:

> Indeed, but this bug affects the version currently in Stable and blocks a
> backport[0][1].

This bug tracker system cannot be used to track bugs in backports. Use
the backports mailing list instead.

Reading the above bug reports, it rather sounds like the problem is with
python3-memcache; this bug is against celery not python3-memcache.

> Moreover every part of python3-celery 3.1.13-3 (in stable) that uses 
> python3-memcache is supposed to be unusuable too. So, this bug remains 
> quite relevant. I think it should be reopened.

This bug was for a very specific reason: the build depends on
python3-memcache needed to be dropped in the stable version. The bug
said this was because python3-memcache would be removed from stable
without providing any evidence that this was going to happen or that
anybody has requested for this to happen.

For some reason you declared this was fixed in version 3.1.18-1. Fixed
but not closed. I have no idea why you did this, I don't see any changes
in 3.1.18-1 related to this bug report. I found this very confusing.

I don't think there is anything that can be done to celery to fix the
issues with the broken python3-memcache. I believe celery will memcache
if told to do so, and this has nothing to do with if python3-memcache is
in the build depends.

python3-memcache needs to be fixed in stable, and I would have thought
this qualified for an update to proposed-updates - in which case there
is no need to drop python3-celery from the build depends - talk to the
release managers about this.

Even if python3-memcache is dropped in stable, we can't update celery in
stable without approval of the release managers, so you still would need
to talk to them.

*If* the release managers agree that the build depends needs to be
dropped for the stable version, we can reopen this bug report at that
time. In the meantime however there is no bug in celery that needs
fixing.

> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788561
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793117
-- 
Brian May <bam at debian.org>