Nishanth Aravamudan <nish.aravamu...@canonical.com> writes: > It seems like celeryd incorrectly only depends on python-celery (which > appears to just the python2 library code), but the init scripts in > celeryd invoke celery and celeryd, which are (now?) in > python-celery-common.
I have pushed a change through to git that will fix this on the next release. However note that I am not entirely happy with celeryd. The problem being that the init.d depends on some project directory that is outside the scope of Debian. As a result choices like python2 or python3 are arbitrary (unless override in the defaults file) and may be wrong for the given project. Or may change unexpectedly. e.g. installing python3-celery will make it default to python3. Would be better I think if the project supplied its own init.d script. -- Brian May <b...@debian.org>
