The dependancies for kombu and billiard are wrong for celery 3.0.21 (and as a result it crashes when you to try to run it). It should be (the ones that need fixing) >=dev-python/kombu-2.5.12[${PYTHON_USEDEP}] >=dev-python/billiard-2.7.3.31[${PYTHON_USEDEP}] Reproducible: Always Steps to Reproduce: 1. emerge -av celery 2. Run some celery script 3. Actual Results: Traceback (most recent call last): File "/usr/bin/celery-python2.7", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 3011, in <module> parse_requirements(__requires__), Environment() File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 626, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: kombu>=2.5.12,<3.0 Expected Results: No error and the worker queue starts. See attached patch. This does not entirely fix the problem however because there is no ebuild for kombu>=2.5.12, so until that's fixed celery-3.0.21 cannot be installed.
Created attachment 355920 [details, diff] Patch for celery-3.0.21 ebuild file.
P.S. I got these requirements from the setup.cfg file from the celery-3.0.21.tar.gz dist file.
*kombu-2.5.12 (15 Aug 2013) 15 Aug 2013; Ian Delaney <idella4@gentoo.org> +kombu-2.5.12.ebuild: bump, needed for celery-3.0.21, corrections & updates to deps kombu is in, try again.
to wranglers of here bugs, AFAIK iksaif has moved on months ago, but since I'm not certain I'll just raise it as a prompt.
Unless I'm missing something this patch has NOT been applied to the ebuild file in question. The main point of this bug is that the requirements in the ebuild are wrong, this has not been fixed. I appreciate the new kombu ebuilds, but that isn't the subject of this bug.
seems to be correctly set in recent ebuilds. If still problems exist, please reopen