Hugo Lefeuvre writes:
> 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.
FYI I believe the correct way to deal with this would be to assign the
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
Hugo Lefeuvre 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
Hi Brian,
> Believe this was fixed in 3.1.18-1. Closing.
Indeed, but this bug affects the version currently in Stable and blocks a
backport[0][1].
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
Package: python3-celery
Version: 3.1.13-3
Severity: important
Dear Maintainer,
python3-celery build-depends on python3-memcache, which will be
soon removed from the stable distribution[0][1] due to an incomplete
Python3 compatibility.
Therefore, python3-celery's build-dependency against
5 matches
Mail list logo