Re: [Python-modules-team] squeeze update of python-django?

2015-11-26 Thread Chris Lamb
> > (I took it in dla-needed.txt but please take it back) > > Well, first come, first served, so go ahead if you want to work on it > right now. Uploaded; apologies for not following up here earlier. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chri

Re: [Python-modules-team] squeeze update of python-django?

2015-11-25 Thread Raphael Hertzog
On Wed, 25 Nov 2015, Chris Lamb wrote: > (I took it in dla-needed.txt but please take it back) Well, first come, first served, so go ahead if you want to work on it right now. Just make sure to integrate your changes in the git repository in the debian/squeeze branch (I assume you still have comm

Re: [Python-modules-team] squeeze update of python-django?

2015-11-25 Thread Chris Lamb
(I took it in dsa-needed.txt but please take it back) On Wed, 25 Nov 2015, at 03:35 PM, Raphael Hertzog wrote: > Hi, > > On Wed, 25 Nov 2015, Ben Hutchings wrote: > > > Think only the changes to django/utils/formats.py will be required. > > > > I already looked at that and decided that the issu

Re: [Python-modules-team] squeeze update of python-django?

2015-11-25 Thread Raphael Hertzog
Hi, On Wed, 25 Nov 2015, Ben Hutchings wrote: > > Think only the changes to django/utils/formats.py will be required. > > I already looked at that and decided that the issue probably did apply > in squeeze, otherwise I wouldn't have bothered you. > > As Raphaël is also on the LTS team, I expect

Re: [Python-modules-team] squeeze update of python-django?

2015-11-25 Thread Ben Hutchings
On Wed, 2015-11-25 at 14:55 +1100, Brian May wrote: > I CCed Raphaël Hertzog as he may have missed the > original email to , which > is normally for automatic messages only. > > > > I think our priorities need to be with the unstable version (which also > has a grave bug), and then the stable v

Re: [Python-modules-team] squeeze update of python-django?

2015-11-24 Thread Brian May
I CCed Raphaël Hertzog as he may have missed the original email to , which is normally for automatic messages only. I think our priorities need to be with the unstable version (which also has a grave bug), and then the stable version. In the meantime however, here is a patch to the change in t