diff --git a/celery-3.0.13.tar.bz2 b/celery-3.0.13.tar.bz2
deleted file mode 100644
index 3629316..0000000
--- a/celery-3.0.13.tar.bz2
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:62b07ba4cdacf9d5674312a21b94ca1c77a9a20b2689f7d3912d1abca31ab513
-size 1136270
diff --git a/celery-3.0.14.tar.bz2 b/celery-3.0.14.tar.bz2
new file mode 100644
index 0000000..6c73d8d
--- /dev/null
+++ b/celery-3.0.14.tar.bz2
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:326c2f558038614fe60c45c5a405b1bc6d3af0c412ef32945238f13dd6bb1ba3
+size 1140293
diff --git a/python-celery.changes b/python-celery.changes
index 3442c6d..33ddc8f 100644
--- a/python-celery.changes
+++ b/python-celery.changes
@@ -1,3 +1,78 @@
+-------------------------------------------------------------------
+Fri Feb  8 20:10:26 UTC 2013 - alexandre@exatati.com.br
+
+- Update to 3.0.14:
+  - Now depends on Kombu 2.5.6
+  - Now depends on billiard 2.7.3.20
+  - execv is now disabled by default.
+    It was causing too many problems for users, you can still enable
+    it using the CELERYD_FORCE_EXECV setting.
+    execv was only enabled when transports other than amqp/redis was used,
+    and it's there to prevent deadlocks caused by mutexes not being released
+    before the process forks.  Sadly it also changes the environment
+    introducing many corner case bugs that is hard to fix without adding
+    horrible hacks.  Deadlock issues are reported far less often than the
+    bugs that execv are causing, so we now disable it by default.
+    Work is in motion to create non-blocking versions of these transports
+    so that execv is not necessary (which is the situation with the amqp
+    and redis broker transports)
+  - Chord exception behavior defined (Issue #1172).
+    From Celery 3.1 the chord callback will change state to FAILURE
+    when a task part of a chord raises an exception.
+    It was never documented what happens in this case,
+    and the actual behavior was very unsatisfactory, indeed
+    it will just forward the exception value to the chord callback.
+    For backward compatibility reasons we do not change to the new
+    behavior in a bugfix release, even if the current behavior was
+    never documented.  Instead you can enable the
+    CELERY_CHORD_PROPAGATES setting to get the new behavior
+    that will be default from Celery 3.1.
+    See more at chord-errors.
+  - worker: Fixes bug with ignored and retried tasks.
+    The on_chord_part_return and Task.after_return callbacks,
+    nor the task_postrun signal should be called when the task was
+    retried/ignored.
+    Fix contributed by Vlad.
+  - GroupResult.join_native now respects the propagate argument.
+  - subtask.id added as an alias to subtask['options'].id
+        >>> s = add.s(2, 2)
+        >>> s.id = 'my-id'
+        >>> s['options']
+        {'task_id': 'my-id'}
+
+        >>> s.id
+        'my-id'
+  - worker: Fixed error `Could not start worker processes` occurring
+    when restarting after connection failure (Issue #1118).
+  - Adds new signal task-retried (Issue #1169).
+  - `celery events --dumper` now handles connection loss.
+  - Will now retry sending the task-sent event in case of connection failure.
+  - amqp backend:  Now uses Message.requeue instead of republishing
+    the message after poll.
+  - New BROKER_HEARTBEAT_CHECKRATE setting introduced to modify the
+    rate at which broker connection heartbeats are monitored.
+    The default value was also changed from 3.0 to 2.0.
+  - celery.events.state.State is now pickleable.
+    Fix contributed by Mher Movsisyan.
+  - celery.datastructures.LRUCache is now pickleable.
+    Fix contributed by Mher Movsisyan.
+  - The stats broadcast command now includes the workers pid.
+    Contributed by Mher Movsisyan.
+  - New conf remote control command to get a workers current configuration.
+    Contributed by Mher Movsisyan.
+  - Adds the ability to modify the chord unlock task's countdown
+    argument (Issue #1146).
+    Contributed by Jun Sakai
+  - beat: The scheduler now uses the now() method of the schedule,
+    so that schedules can provide a custom way to get the current date and time.
+    Contributed by Raphaël Slinckx
+  - Fixed pickling of configuration modules on Windows or when execv is used
+    (Issue #1126).
+  - Multiprocessing logger is now configured with loglevel ERROR
+    by default.
+    Since 3.0 the multiprocessing loggers were disabled by default
+    (only configured when the MP_LOG environment variable was set).
+
 -------------------------------------------------------------------
 Mon Jan  7 16:34:24 UTC 2013 - alexandre@exatati.com.br
 
diff --git a/python-celery.spec b/python-celery.spec
index b2afd98..3f4c48f 100644
--- a/python-celery.spec
+++ b/python-celery.spec
@@ -17,7 +17,7 @@
 
 
 Name:           python-celery
-Version:        3.0.13
+Version:        3.0.14
 Release:        0
 Url:            http://celeryproject.org
 Summary:        Distributed Task Queue
@@ -33,7 +33,7 @@ BuildRequires:  python-devel
 BuildRequires:  python-distribute
 BuildRequires:  python-eventlet
 BuildRequires:  python-gevent
-BuildRequires:  python-kombu >= 2.4.8
+BuildRequires:  python-kombu >= 2.5.6
 BuildRequires:  python-mock
 BuildRequires:  python-nose-cover3
 BuildRequires:  python-pyOpenSSL
@@ -48,7 +48,7 @@ Requires:       python-importlib
 Requires:       python-ordereddict
 %endif
 Requires:       python-anyjson
-Requires:       python-billiard >= 2.7.3.19
+Requires:       python-billiard >= 2.7.3.20
 Requires:       python-dateutil
 Recommends:     python-curses
 Recommends:     python-pyOpenSSL