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

Hugo Lefeuvre hle at hugo6390.org
Sun Dec 20 13:06:21 UTC 2015


Hi,

Please, excuse the late answer.

> > 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.

Sorry, I've been unclear. I intended to highlight the fact that there aren't 
any problems on Unstable and Testing. The only distribution being affected by
this "bug" is Stable.

> 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.

I understand, however I though it was better to speak about it here before I 
ask the release managers if they agree to drop python3-celery from the build-depends.

Cheers,
 Hugo

-- 
      Hugo Lefeuvre (hugo6390)    |    www.hugo6390.org
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20151220/f0afc622/attachment.sig>


More information about the Python-modules-team mailing list