The dependencies for this package appear to be wrong
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
celery (Debian) |
Fix Released
|
Unknown
|
|||
celery (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 16.04.2 LTS
celeryd:
Installed: 3.1.20-1
Candidate: 3.1.20-1
Version table:
*** 3.1.20-1 500
500 http://
100 /var/lib/
The package 'celeryd' (which this bug reporting system claims not to exist even though it does) seems to have an undeclared dependency on python-
The package has a declared dependency on python-celery when I think in fact it should depend on python-celery *OR* python3-celery - meaning if you want to use celery with python3 then the package insists on you installing celery under python2 even though it's not going to be used, and also that it's very non-obvious how you use celery with python3.
Changed in celery (Ubuntu): | |
status: | New → Triaged |
Changed in celery (Debian): | |
status: | Unknown → New |
Changed in celery (Debian): | |
status: | New → Fix Committed |
Changed in celery (Debian): | |
status: | Fix Committed → Fix Released |
Hello and thank you for filing this bug report.
celery is the source package name, which is why the bug reporting tool wouldn't let you report a bug against celeryd (a binary package name).
TBH, there seem to be a lot of issues with /etc/init.d/celeryd (it uses non-dash compatible syntax which throws an error, at least).
I think if celeryd were to depend on python- celery- common, you'd automatically obtain your requested change because python- celery- common:
Depends: python3-celery (= 3.1.23-5) | python-celery (= 3.1.23-5)
I will ask the upstream developers about this.