Canonical repo moved to github.com/celery/celery

Changelog

@@ -217,7 +217,7 @@ Security Fixes
 
 
 .. _`CELERYSA-0001`:
-    http://github.com/ask/celery/tree/master/docs/sec/CELERYSA-0001.txt
+    http://github.com/celery/celery/tree/master/docs/sec/CELERYSA-0001.txt
 
 .. _v244-fixes:
 
@@ -592,7 +592,7 @@ Security Fixes
 
 
 .. _`CELERYSA-0001`:
-    http://github.com/ask/celery/tree/master/docs/sec/CELERYSA-0001.txt
+    http://github.com/celery/celery/tree/master/docs/sec/CELERYSA-0001.txt
 
 Fixes
 -----
@@ -633,7 +633,7 @@ News
 * Improved Contributing guide.
 
     If you'd like to contribute to Celery you should read this
-    guide: http://ask.github.com/celery/contributing.html
+    guide: http://celery.github.com/celery/contributing.html
 
     We are looking for contributors at all skill levels, so don't
     hesitate!
@@ -948,7 +948,7 @@ Security Fixes
 
 
 .. _`CELERYSA-0001`:
-    http://github.com/ask/celery/tree/master/docs/sec/CELERYSA-0001.txt
+    http://github.com/celery/celery/tree/master/docs/sec/CELERYSA-0001.txt
 
 .. _version-2.2.7:
 
@@ -2634,7 +2634,7 @@ Experimental
 
 * Added generic init.d script using `celeryd-multi`
 
-    http://github.com/ask/celery/tree/master/contrib/generic-init.d/celeryd
+    http://github.com/celery/celery/tree/master/contrib/generic-init.d/celeryd
 
 .. _v210-documentation:
 
@@ -3209,7 +3209,7 @@ Backward incompatible changes
     =====================================  =====================================
 
 .. _`deprecation timeline`:
-    http://ask.github.com/celery/internals/deprecation.html
+    http://celery.github.com/celery/internals/deprecation.html
 
 * The `celery.task.rest` module has been removed, use :mod:`celery.task.http`
   instead (as scheduled by the `deprecation timeline`_).
@@ -4420,7 +4420,7 @@ News
 * celeryd now sends events if enabled with the `-E` argument.
 
     Excellent for monitoring tools, one is already in the making
-    (http://github.com/ask/celerymon).
+    (http://github.com/celery/celerymon).
 
     Current events include: worker-heartbeat,
     task-[received/succeeded/failed/retried],
@@ -4733,7 +4733,7 @@ Important changes
     See `Cookbook: Retrying Tasks`_ for more information.
 
 .. _`Cookbook: Retrying Tasks`:
-    http://ask.github.com/celery/cookbook/task-retries.html
+    http://celery.github.com/celery/cookbook/task-retries.html
 
 * We now have an AMQP result store backend.
 
@@ -5168,7 +5168,7 @@ arguments, so be sure to flush your task queue before you upgrade.
 
 .. _`Can I send some tasks to only some servers?`:
         http://bit.ly/celery_AMQP_routing
-.. _`FAQ`: http://ask.github.com/celery/faq.html
+.. _`FAQ`: http://celery.github.com/celery/faq.html
 
 * Task errors are now logged using log level `ERROR` instead of `INFO`,
   and stacktraces are dumped. Thanks to Grégoire Cachet.

FAQ

@@ -89,14 +89,11 @@ Do I have to use AMQP/RabbitMQ?
 **Answer**: No.
 
 You can also use Redis, Beanstalk, CouchDB, MongoDB or an SQL database,
-see `Using other queues`_.
+see :ref:`brokers`.
 
 These "virtual transports" may have limited broadcast and event functionality.
 For example remote control commands only works with AMQP and Redis.
 
-.. _`Using other queues`:
-    http://ask.github.com/celery/tutorials/otherqueues.html
-
 Redis or a database won't perform as well as
 an AMQP broker. If you have strict reliability requirements you are
 encouraged to use RabbitMQ or another AMQP broker. Redis/database also use
@@ -125,7 +122,7 @@ information you can even create simple web servers that enable preloading of
 code. See: `User Guide: Remote Tasks`_.
 
 .. _`User Guide: Remote Tasks`:
-    http://ask.github.com/celery/userguide/remote-tasks.html
+    http://celery.github.com/celery/userguide/remote-tasks.html
 
 .. _faq-troubleshooting:
 

README.rst

@@ -7,7 +7,7 @@
 :Version: 2.6.0rc4
 :Web: http://celeryproject.org/
 :Download: http://pypi.python.org/pypi/celery/
-:Source: http://github.com/ask/celery/
+:Source: http://github.com/celery/celery/
 :Keywords: task queue, job queue, asynchronous, rabbitmq, amqp, redis,
   python, webhooks, queue, distributed
 
@@ -84,7 +84,7 @@ integration packages:
 .. _`Tornado`: http://www.tornadoweb.org/
 .. _`tornado-celery`: http://github.com/mher/tornado-celery/
 .. _`operate with other languages using webhooks`:
-    http://ask.github.com/celery/userguide/remote-tasks.html
+    http://celery.github.com/celery/userguide/remote-tasks.html
 .. _`limited support`:
     http://kombu.readthedocs.org/en/latest/introduction.html#transport-comparison
 
@@ -230,7 +230,7 @@ Documentation
 The `latest documentation`_ with user guides, tutorials and API reference
 is hosted at Github.
 
-.. _`latest documentation`: http://ask.github.com/celery/
+.. _`latest documentation`: http://celery.github.com/celery/
 
 .. _celery-installation:
 
@@ -299,7 +299,7 @@ Using the development version
 
 You can clone the repository by doing the following::
 
-    $ git clone https://github.com/ask/celery
+    $ git clone https://github.com/celery/celery
     $ cd celery
     $ python setup.py develop
 
@@ -307,7 +307,7 @@ The development version will usually also depend on the development
 version of `kombu`_, the messaging framework Celery uses
 to send and receive messages, so you should also install that from git::
 
-    $ git clone https://github.com/ask/kombu
+    $ git clone https://github.com/celery/kombu
     $ cd kombu
     $ python setup.py develop
 
@@ -345,21 +345,21 @@ Bug tracker
 ===========
 
 If you have any suggestions, bug reports or annoyances please report them
-to our issue tracker at http://github.com/ask/celery/issues/
+to our issue tracker at http://github.com/celery/celery/issues/
 
 .. _wiki:
 
 Wiki
 ====
 
-http://wiki.github.com/ask/celery/
+http://wiki.github.com/celery/celery/
 
 .. _contributing-short:
 
 Contributing
 ============
 
-Development of `celery` happens at Github: http://github.com/ask/celery
+Development of `celery` happens at Github: http://github.com/celery/celery
 
 You are highly encouraged to participate in the development
 of `celery`. If you don't like Github (for some reason) you're welcome
@@ -368,7 +368,7 @@ to send regular patches.
 Be sure to also read the `Contributing to Celery`_ section in the
 documentation.
 
-.. _`Contributing to Celery`: http://ask.github.com/celery/contributing.html
+.. _`Contributing to Celery`: http://celery.github.com/celery/contributing.html
 
 .. _license:
 

celery/apps/worker.py

@@ -249,7 +249,7 @@ class Worker(configurated):
             # into the background.
             if self.app.IS_OSX:
                 # OS X can't exec from a process using threads.
-                # See http://github.com/ask/celery/issues#issue/152
+                # See http://github.com/celery/celery/issues#issue/152
                 install_HUP_not_supported_handler(worker)
             else:
                 install_worker_restart_handler(worker)
@@ -260,7 +260,7 @@ class Worker(configurated):
         install_rdb_handler()
 
     def osx_proxy_detection_workaround(self):
-        """See http://github.com/ask/celery/issues#issue/161"""
+        """See http://github.com/celery/celery/issues#issue/161"""
         os.environ.setdefault("celery_dummy_proxy", "set_by_celeryd")
 
     def set_process_status(self, info):

contrib/supervisord/celerybeat.conf

@@ -4,7 +4,7 @@
 
 ; NOTE: If you're using Django, you shouldn't use this file.
 ; Use
-; http://github.com/ask/django-celery/tree/master/contrib/supervisord/celerybeat.conf
+; http://github.com/celery/django-celery/tree/master/contrib/supervisord/celerybeat.conf
 ; instead!
 
 [program:celerybeat]

contrib/supervisord/celeryd.conf

@@ -4,7 +4,7 @@
 
 ; NOTE: If you're using Django, you shouldn't use this file.
 ; Use
-; http://github.com/ask/django-celery/tree/master/contrib/supervisord/celeryd.conf
+; http://github.com/celery/django-celery/tree/master/contrib/supervisord/celeryd.conf
 ; instead!
 
 [program:celery]

docs/.templates/page.html

@@ -12,7 +12,7 @@
         {% else %}
         <p>
         This document describes Celery {{ version }}. For development docs,
-        <a href="http://ask.github.com/celery/{{ pagename }}{{ file_suffix }}">go here</a>.
+        <a href="http://celery.github.com/celery/{{ pagename }}{{ file_suffix }}">go here</a>.
         </p>
     {% endif %}
 

docs/community.rst

@@ -21,14 +21,14 @@ Resources
 Who's using Celery
 ------------------
 
-http://wiki.github.com/ask/celery/using
+http://wiki.github.com/celery/celery/using
 
 .. _res-wiki:
 
 Wiki
 ----
 
-http://wiki.github.com/ask/celery/
+http://wiki.github.com/celery/celery/
 
 .. _res-stackoverflow:
 

docs/conf.py

@@ -105,5 +105,5 @@ html_sidebars = {
 
 if False:
     issuetracker = "github"
-    issuetracker_project = "ask/celery"
+    issuetracker_project = "celery/celery"
     issuetracker_issue_pattern = r'[Ii]ssue #(\d+)'

docs/contributing.rst

@@ -151,11 +151,10 @@ Issue Trackers
 Bugs for a package in the Celery ecosystem should be reported to the relevant
 issue tracker.
 
-* Celery: http://github.com/ask/celery/issues/
-* Django-Celery: http://github.com/ask/django-celery/issues
-* Flask-Celery: http://github.com/ask/flask-celery/issues
+* Celery: http://github.com/celery/celery/issues/
+* Django-Celery: http://github.com/celery/django-celery/issues
 * Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues
-* Kombu: http://github.com/ask/kombu/issues
+* Kombu: http://github.com/celery/kombu/issues
 
 If you are unsure of the origin of the bug you can ask the
 :ref:`mailing-list`, or just use the Celery issue tracker.
@@ -180,12 +179,12 @@ Branches
 
 Current active version branches:
 
-* master (http://github.com/ask/celery/tree/master)
-* 3.0-devel (http://github.com/ask/celery/tree/3.0-devel)
+* master (http://github.com/celery/celery/tree/master)
+* 3.0-devel (http://github.com/celery/celery/tree/3.0-devel)
 
 You can see the state of any branch by looking at the Changelog:
 
-    https://github.com/ask/celery/blob/master/Changelog
+    https://github.com/celery/celery/blob/master/Changelog
 
 If the branch is in active development the topmost version info should
 contain metadata like::
@@ -305,7 +304,7 @@ When the repository is cloned enter the directory to set up easy access
 to upstream changes::
 
     $ cd celery
-    $ git remote add upstream git://github.com/ask/celery.git
+    $ git remote add upstream git://github.com/celery/celery.git
     $ git fetch upstream
 
 If you need to pull in new changes from upstream you should
@@ -634,6 +633,14 @@ is following the conventions.
 Contacts
 ========
 
+This is a list of people that can be contacted for questions
+regarding the official git repositories, PyPI packages
+Read the Docs pages.
+
+If the issue is not an emergency then it is better
+to :ref:`report an issue <reporting-bugs>`.
+
+
 Committers
 ----------
 
@@ -682,7 +689,7 @@ Packages
 celery
 ------
 
-:git: https://github.com/ask/celery
+:git: https://github.com/celery/celery
 :CI: http://travis-ci.org/#!/ask/celery
 :PyPI: http://pypi.python.org/pypi/celery
 :docs: http://docs.celeryproject.org
@@ -692,7 +699,7 @@ kombu
 
 Messaging framework.
 
-:git: https://github.com/ask/kombu
+:git: https://github.com/celery/kombu
 :CI: http://travis-ci.org/#!/ask/kombu
 :PyPI: http://pypi.python.org/pypi/kombu
 :docs: http://kombu.readthedocs.org
@@ -703,7 +710,7 @@ billiard
 Fork of multiprocessing containing improvements
 that will eventually be merged into the Python stdlib.
 
-:git: https://github.com/ask/billiard
+:git: https://github.com/celery/billiard
 :PyPI: http://pypi.python.org/pypi/billiard
 
 librabbitmq
@@ -719,7 +726,7 @@ celerymon
 
 Celery monitor web-service.
 
-:git: https://github.com/ask/celerymon
+:git: https://github.com/celery/celerymon
 :PyPI: http://pypi.python.org/pypi/celerymon
 
 django-celery
@@ -727,7 +734,7 @@ django-celery
 
 Django <-> Celery Integration.
 
-:git: https://github.com/ask/django-celery
+:git: https://github.com/celery/django-celery
 :PyPI: http://pypi.python.org/pypi/django-celery
 :docs: http://docs.celeryproject.org/en/latest/django
 
@@ -736,7 +743,7 @@ cl
 
 Actor framework.
 
-:git: https://github.com/ask/cl
+:git: https://github.com/celery/cl
 :PyPI: http://pypi.python.org/pypi/cl
 
 cyme

docs/cookbook/daemonizing.rst

@@ -22,7 +22,7 @@ This directory contains generic bash init scripts for :program:`celeryd`,
 that should run on Linux, FreeBSD, OpenBSD, and other Unix platforms.
 
 .. _`contrib/generic-init.d/`:
-    http://github.com/ask/celery/tree/master/contrib/generic-init.d/
+    http://github.com/celery/celery/tree/master/contrib/generic-init.d/
 
 .. _generic-initd-celeryd:
 
@@ -295,7 +295,7 @@ actual resulting output::
 * `contrib/supervisord/`_
 
 .. _`contrib/supervisord/`:
-    http://github.com/ask/celery/tree/master/contrib/supervisord/
+    http://github.com/celery/celery/tree/master/contrib/supervisord/
 .. _`supervisord`: http://supervisord.org/
 
 .. _daemon-launchd:
@@ -306,7 +306,7 @@ launchd (OS X)
 * `contrib/mac/`_
 
 .. _`contrib/mac/`:
-    http://github.com/ask/celery/tree/master/contrib/mac/
+    http://github.com/celery/celery/tree/master/contrib/mac/
 
 
 .. _daemon-windows:

docs/includes/installation.txt

@@ -27,4 +27,4 @@ Using the development version
 
 You can clone the repository by doing the following::
 
-    $ git clone git://github.com/ask/celery.git
+    $ git clone https://github.com/celery/celery

docs/includes/introduction.txt

@@ -1,7 +1,7 @@
 :Version: 2.6.0rc4
 :Web: http://celeryproject.org/
 :Download: http://pypi.python.org/pypi/celery/
-:Source: http://github.com/ask/celery/
+:Source: http://github.com/celery/celery/
 :Keywords: task queue, job queue, asynchronous, rabbitmq, amqp, redis,
   python, webhooks, queue, distributed
 
@@ -78,7 +78,7 @@ integration packages:
 .. _`Tornado`: http://www.tornadoweb.org/
 .. _`tornado-celery`: http://github.com/mher/tornado-celery/
 .. _`operate with other languages using webhooks`:
-    http://ask.github.com/celery/userguide/remote-tasks.html
+    http://celery.github.com/celery/userguide/remote-tasks.html
 .. _`limited support`:
     http://kombu.readthedocs.org/en/latest/introduction.html#transport-comparison
 
@@ -225,7 +225,7 @@ Documentation
 The `latest documentation`_ with user guides, tutorials and API reference
 is hosted at Github.
 
-.. _`latest documentation`: http://ask.github.com/celery/
+.. _`latest documentation`: http://celery.github.com/celery/
 
 .. _celery-installation:
 
@@ -294,7 +294,7 @@ Using the development version
 
 You can clone the repository by doing the following::
 
-    $ git clone https://github.com/ask/celery
+    $ git clone https://github.com/celery/celery
     $ cd celery
     $ python setup.py develop
 
@@ -302,7 +302,7 @@ The development version will usually also depend on the development
 version of `kombu`_, the messaging framework Celery uses
 to send and receive messages, so you should also install that from git::
 
-    $ git clone https://github.com/ask/kombu
+    $ git clone https://github.com/celery/kombu
     $ cd kombu
     $ python setup.py develop
 

docs/includes/resources.txt

@@ -30,21 +30,21 @@ Bug tracker
 ===========
 
 If you have any suggestions, bug reports or annoyances please report them
-to our issue tracker at http://github.com/ask/celery/issues/
+to our issue tracker at http://github.com/celery/celery/issues/
 
 .. _wiki:
 
 Wiki
 ====
 
-http://wiki.github.com/ask/celery/
+http://wiki.github.com/celery/celery/
 
 .. _contributing-short:
 
 Contributing
 ============
 
-Development of `celery` happens at Github: http://github.com/ask/celery
+Development of `celery` happens at Github: http://github.com/celery/celery
 
 You are highly encouraged to participate in the development
 of `celery`. If you don't like Github (for some reason) you're welcome
@@ -53,7 +53,7 @@ to send regular patches.
 Be sure to also read the `Contributing to Celery`_ section in the
 documentation.
 
-.. _`Contributing to Celery`: http://ask.github.com/celery/contributing.html
+.. _`Contributing to Celery`: http://celery.github.com/celery/contributing.html
 
 .. _license:
 

docs/releases/1.0/announcement.rst

@@ -28,7 +28,7 @@ databases is also available.
 Features
 --------
 
-See http://ask.github.com/celery/getting-started/introduction.html#features
+See http://celery.github.com/celery/getting-started/introduction.html#features
 
 Stable API
 ==========
@@ -50,7 +50,7 @@ that existed in Celery 1.0:
 See the `Celery Deprecation Timeline`_ for a list of pending removals.
 
 .. _`Celery Deprecation Timeline`:
-    http://ask.github.com/celery/internals/deprecation.html
+    http://celery.github.com/celery/internals/deprecation.html
 
 What's new?
 ===========
@@ -76,7 +76,7 @@ What's new?
     workers. This is the basis for the new real-time web monitor we're working on
     (`celerymon`_).
 
-.. _`celerymon`: http://github.com/ask/celerymon/
+.. _`celerymon`: http://github.com/celery/celerymon/
 
 * Rate limiting
 
@@ -137,7 +137,7 @@ the `changelog`_. This document contains crucial information for those
 upgrading from a previous version of Celery, so be sure to read the entire
 change set before you continue.
 
-.. _`changelog`: http://ask.github.com/celery/changelog.html
+.. _`changelog`: http://celery.github.com/celery/changelog.html
 
 **TIP:** If you install the :mod:`setproctitle` module you can see which
 task each worker process is currently executing in `ps` listings.
@@ -154,9 +154,9 @@ Resources
 
 * Changelog: http://docs.celeryproject.org/changelog.html
 
-* Code: http://github.com/ask/celery/
+* Code: http://github.com/celery/celery/
 
-* FAQ: http://ask.github.com/celery/faq.html
+* FAQ: http://celery.github.com/celery/faq.html
 
 * Mailing-list: http://groups.google.com/group/celery-users
 

docs/userguide/concurrency/eventlet.rst

@@ -59,5 +59,5 @@ some examples taking use of Eventlet support.
     http://en.wikipedia.org/wiki/Asynchronous_I/O#Select.28.2Fpoll.29_loops
 .. _`Coroutines`: http://en.wikipedia.org/wiki/Coroutine
 .. _`Eventlet examples`:
-    https://github.com/ask/celery/tree/master/examples/eventlet
+    https://github.com/celery/celery/tree/master/examples/eventlet
 

docs/userguide/monitoring.rst

@@ -333,7 +333,7 @@ or help this project in any way, please get in touch!
 :Tip: The Django admin monitor can be used even though you're not using
       Celery with a Django project.  See :ref:`monitoring-nodjango`.
 
-.. _`celerymon`: http://github.com/ask/celerymon/
+.. _`celerymon`: http://github.com/celery/celerymon/
 
 .. _monitoring-rabbitmq:
 

docs/userguide/remote-tasks.rst

@@ -119,4 +119,4 @@ Since applying tasks can be done via HTTP using the
 :func:`djcelery.views.apply` view, executing tasks from other languages is easy.
 For an example service exposing tasks via HTTP you should have a look at
 `examples/celery_http_gateway` in the Celery distribution:
-http://github.com/ask/celery/tree/master/examples/celery_http_gateway/
+http://github.com/celery/celery/tree/master/examples/celery_http_gateway/

docs/whatsnew-2.6.rst

@@ -67,8 +67,8 @@ for the no-execv patch to work.
 - Issue #625
 - Issue #627
 - Issue #640
-- `django-celery #122 <http://github.com/ask/django-celery/issues/122`
-- `django-celery #124 <http://github.com/ask/django-celery/issues/122`
+- `django-celery #122 <http://github.com/celery/django-celery/issues/122`
+- `django-celery #124 <http://github.com/celery/django-celery/issues/122`
 
 Last version to support Python 2.5
 ----------------------------------

funtests/setup.py

@@ -41,7 +41,7 @@ setup(
     description="Functional test suite for Celery",
     author="Ask Solem",
     author_email="ask@celeryproject.org",
-    url="http://github.com/ask/celery",
+    url="http://github.com/celery/celery",
     platforms=["any"],
     packages=[],
     data_files=[],

requirements/dev.txt

@@ -1,3 +1,3 @@
-https://github.com/ask/billiard/zipball/master
-https://github.com/ask/kombu/zipball/master
-https://github.com/ask/celery/zipball/master
+https://github.com/celery/billiard/zipball/master
+https://github.com/celery/kombu/zipball/master
+https://github.com/celery/celery/zipball/master

requirements/test.txt

@@ -7,4 +7,4 @@ redis
 pymongo
 SQLAlchemy
 PyOpenSSL
-https://github.com/ask/kombu/zipball/master
+https://github.com/celery/kombu/zipball/master

tox.ini

@@ -16,7 +16,7 @@ commands = {toxinidir}/contrib/release/removepyc.sh {toxinidir}
            {envbindir}/pip install                              \
                 --download-cache={toxworkdir}/_download         \
                 -r{toxinidir}/requirements/test-py3k.txt
-           pip install -U https://github.com/ask/kombu/zipball/master
+           pip install -U https://github.com/celery/kombu/zipball/master
 
            {toxinidir}/contrib/release/py3k-run-tests {toxinidir}
 
@@ -30,7 +30,7 @@ commands = {toxinidir}/contrib/release/removepyc.sh {toxinidir}
            {envbindir}/pip install                              \
                 --download-cache={toxworkdir}/_download         \
                 -r{toxinidir}/requirements/test-py3k.txt
-           pip install -U https://github.com/ask/kombu/zipball/master
+           pip install -U https://github.com/celery/kombu/zipball/master
 
            {toxinidir}/contrib/release/py3k-run-tests {toxinidir}
 
@@ -39,7 +39,7 @@ basepython = python2.7
 deps = -r{toxinidir}/requirements/default.txt
        -r{toxinidir}/requirements/test.txt
 commands = {toxinidir}/contrib/release/removepyc.sh {toxinidir}
-           pip install -U https://github.com/ask/kombu/zipball/master
+           pip install -U https://github.com/celery/kombu/zipball/master
            nosetests --with-xunit                               \
                      --xunit-file={toxinidir}/nosetests.xml     \
                      --with-coverage3 --cover3-xml              \
@@ -52,7 +52,7 @@ deps = -r{toxinidir}/requirements/default.txt
        -r{toxinidir}/requirements/py26.txt
        -r{toxinidir}/requirements/test.txt
 commands = {toxinidir}/contrib/release/removepyc.sh {toxinidir}
-           pip install -U https://github.com/ask/kombu/zipball/master
+           pip install -U https://github.com/celery/kombu/zipball/master
            nosetests --with-xunit                               \
                      --xunit-file={toxinidir}/nosetests.xml     \
                      --with-coverage3 --cover3-xml              \
@@ -65,7 +65,7 @@ deps = -r{toxinidir}/requirements/default.txt
        -r{toxinidir}/requirements/py25.txt
        -r{toxinidir}/requirements/test.txt
 commands = {toxinidir}/contrib/release/removepyc.sh {toxinidir}
-           pip install -U https://github.com/ask/kombu/zipball/master
+           pip install -U https://github.com/celery/kombu/zipball/master
            nosetests --with-xunit                               \
                      --xunit-file={toxinidir}/nosetests.xml     \
                      --with-coverage3 --cover3-xml              \
@@ -77,7 +77,7 @@ basepython = pypy
 deps = -r{toxinidir}/requirements/default.txt
        -r{toxinidir}/requirements/test-pypy.txt
 commands = {toxinidir}/contrib/release/removepyc.sh {toxinidir}
-           pip install -U https://github.com/ask/kombu/zipball/master
+           pip install -U https://github.com/celery/kombu/zipball/master
            nosetests --with-xunit                               \
                      --xunit-file={toxinidir}/nosetests.xml     \
                      --with-coverage3 --cover3-xml              \