Hello,

I just tidied up this bug. It started off as a Django1.7 bug, then it got
retitled to a Python3 bug.

Then I wondered if maybe I should have cloned it, and retitled the original
back to the original value, and closed it. If you want to refine my
efforts, feel free to do so.

Thanks


---------- Forwarded message ----------
From: Debian Bug Tracking System <ow...@bugs.debian.org>
Date: 9 September 2014 16:06
Subject: Processed: not a django1.7 bug
To: Brian May <br...@microcomaustralia.com.au>


Processing commands for cont...@bugs.debian.org:

> user python-dja...@packages.debian.org
Setting user to python-dja...@packages.debian.org (was
br...@microcomaustralia.com.au).
> usertag 755642 -django17
Usertags were: django17.
Usertags are now: .
> thanks
Stopping processing here.

Please contact me if you need assistance.
--
755642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



-- 
Brian May <br...@microcomaustralia.com.au>

Reply via email to