Your message dated Sun, 17 Aug 2014 15:00:07 +0000
with message-id <[email protected]>
and subject line Bug#755596: fixed in django-celery 3.1.10-2
has caused the Debian Bug report #755596,
regarding django-celery: Please ensure it works with Django 1.7
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 [email protected]
immediately.)


-- 
755596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755596
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: django-celery
Version: 3.1.10-1
Severity: important
User: [email protected]
Usertags: django17

Hello,

your package django-celery depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.

--- End Message ---
--- Begin Message ---
Source: django-celery
Source-Version: 3.1.10-2

We believe that the bug you reported is fixed in the latest version of
django-celery, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Brian May <[email protected]> (supplier of updated django-celery package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 13 Aug 2014 14:48:09 +1000
Source: django-celery
Binary: python-django-celery python3-django-celery python-django-celery-doc
Architecture: source all
Version: 3.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
<[email protected]>
Changed-By: Brian May <[email protected]>
Description:
 python-django-celery - Celery integration for Django
 python-django-celery-doc - Celery integration for Django (Documentation)
 python3-django-celery - Celery integration for Django
Closes: 755596
Changes:
 django-celery (3.1.10-2) unstable; urgency=medium
 .
   * Python3 package.
   * Fix django1.7 compatibility issue (Closes: #755596).
Checksums-Sha1:
 d0a00f0a4a93bfc62c5e4cd9ccead27959e7d56f 2618 django-celery_3.1.10-2.dsc
 528c4f0bde53cec186ffff91f741c9ddda9df401 76323 django-celery_3.1.10.orig.tar.gz
 a39d457a99f563e53db863018ae11db40e073309 6952 
django-celery_3.1.10-2.debian.tar.xz
 31c857e4ac79ca1f78b74105cd1bb2e907ef408d 52506 
python-django-celery_3.1.10-2_all.deb
 8418bb1885151300d4b244efac9bf461710a9f4e 48406 
python3-django-celery_3.1.10-2_all.deb
 28b9505f88850ba830410a12c8e8fe05d91b0296 68584 
python-django-celery-doc_3.1.10-2_all.deb
Checksums-Sha256:
 dddcf8937ff2cd05d68291eb78a7b26263d65ed755d0b242275f8567946e463a 2618 
django-celery_3.1.10-2.dsc
 0c724d1c9c01b1f77ca47f84d2a35f63f8ce8e29b85fb578d7465f86eb8a9180 76323 
django-celery_3.1.10.orig.tar.gz
 00c75db56de922b5da556751623c6d06f141b1287ef5adeb95e0f34df1a54f16 6952 
django-celery_3.1.10-2.debian.tar.xz
 12a3559c4777fa814b08d6dd009106ebdbe497ad7e1a7246b5e5d54dd24ca1c9 52506 
python-django-celery_3.1.10-2_all.deb
 368f7278d786710cf6d6066f932021a4d1789084ce9d0be8e2ac81c749638b7f 48406 
python3-django-celery_3.1.10-2_all.deb
 0c69e18737aff09807a1994cec2f75588e9830fe432bde73ab19828e8e5d0c8e 68584 
python-django-celery-doc_3.1.10-2_all.deb
Files:
 5f8b91810f2251144df79c34d21ceb00 52506 python optional 
python-django-celery_3.1.10-2_all.deb
 187854229a53c68fae633a1e710f3d7e 48406 python optional 
python3-django-celery_3.1.10-2_all.deb
 7227d3cc402805f684bcfeee87cd4271 68584 doc optional 
python-django-celery-doc_3.1.10-2_all.deb
 1634348d20df683325c4d683677e72b9 2618 python optional 
django-celery_3.1.10-2.dsc
 82435ce3900868c11e250a57360d514e 76323 python optional 
django-celery_3.1.10.orig.tar.gz
 1f5443642f83f203be21bc944aed67ad 6952 python optional 
django-celery_3.1.10-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJT7/6UAAoJEJyE7hq50CY2fa8QALJfjSkx4GK5XAjwh3TP4cJ3
rlhlG3/vxhb3ruQevIhnQJhMVZJ9Ld9sdkDyL3fJY+7hRDv6N+TWKdAGm0Mqdqmc
vfqaWelpuY4NWosGfIqfvyXJLbjGW92Xhgfp8TfLw3C76GHActoiFoHhLcIjuMV5
vPOEMknGgb1+G2zvFtnOrTvRP4ZhMU2+l/q29AHqOP+dhKofv55T+Fmdj6kCA28h
U4KWQcfjNDb0bNNiOjTi2QdGz1NOvHRZZoBAGG/f7Wji2wTyqpr1QzuFz8AIIb/P
pQXk72YRqFGU9gjk8lIHw2iT7wDG3Cr8L0hIyNaY3T+eLwKXB9OAe2VEUCTywszv
0x/MKzckYyJtBf2VWm8g7byIglum5e8rIM0vFw4QYgmUTaWyMkfvH2RFWmGA3Scl
dWexqw46DBQgsTiNJKwj+1NVoSOtisgYXY9W+XZiwJTZR1b0aIE0ZFJFXVXqYwzp
XCWHoxQIn9GCr8rs5CwUCI4gsvHCzVfL+slmNfwgwHSMg8gfXrwCA8Uof41QaM5l
rFH4jdJwTzxbBqhIb8Jo18/XoM50cSdxaAjnXLlgqHtSl402d/aE2xciyD3rh7rV
Bg5sHZyjJSvfli768CiHlEA6+icJebD80tn2BANIbpsy6aUFF6cdZR4K+ly7NiQx
D+zvzyDq13CWRW64kaEm
=mRKW
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Reply via email to