[Python-modules-team] Bug#858305: Bug#858305: celeryd: celerdy should depend on python-celery-common?

[Nish Aravamudan]

On 21.03.2017 [21:26:23 +1100], Brian May wrote:
> Nishanth Aravamudan <nish.aravamudan at 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.

Thank you!
 
> 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.

Agreed, this is the first package I've come across that uses the
upstream's initscripts directly (rather than, say, a copy).

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd