Hello, I'm sorry for the delay. Using "./manage.py runserver" the new version I packaged in svn works fine and is theoretically ready to be uploaded, but there seems to be something wrong with the Apache config because I ran into some obscure bug when testing it.
Unfortunately I cannot be any more specific or fix the packages at the moment because my dev box broke and I have to fix it first. I hope to get that done next week, but I'm afraid I won't be able to look into the packages any sooner. :( Sorry again. Michael ---- Raphael Hertzog schrieb ---- >Control: severity -1 serious > >Hello, > >On Tue, 22 Jul 2014, hert...@debian.org wrote: >> 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. > >Django 1.7 is now in unstable for a week already and I just discovered >that it never migrated to testing because mumble-django depends on >python-django (<< 1.7). > >There's a new upstream release 2.12 which brings Django 1.7 compatibility: >https://bitbucket.org/Svedrin/mumble-django/commits/d3cbd8b28847a5f6ae6016b249852f82857d710c > >I see in fact that the new release has been prepared in SVN but never >uploaded. Can you do that ASAP? Please set urgency=high in >debian/changelog in order to not further delay the migration of Django 1.7 >to Jessie. > >If you want me to handle the upload, let me know! > >Thank you! >-- >Raphaël Hertzog ◈ Debian Developer > >Discover the Debian Administrator's Handbook: >→ http://debian-handbook.info/get/
