[Python-modules-team] Bug#711338: marked as done (django-celery: FTBFS: django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.)

Sun Dec 22 04:03:05 UTC 2013

Your message dated Sun, 22 Dec 2013 04:00:10 +0000
with message-id <E1VuaD4-0005L2-80 at franck.debian.org>
and subject line Bug#711338: fixed in celery 3.1.6-1
has caused the Debian Bug report #711338,
regarding django-celery: FTBFS: django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)

-- 
711338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711338
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Jakub Wilk <jwilk at debian.org>
Subject: django-celery: FTBFS: django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
Date: Thu, 6 Jun 2013 14:17:27 +0200
Size: 4586
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20131222/ad2daedd/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Fladischer <FladischerMichael at fladi.at>
Subject: Bug#711338: fixed in celery 3.1.6-1
Date: Sun, 22 Dec 2013 04:00:10 +0000
Size: 7764
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20131222/ad2daedd/attachment-0003.mht>