On 13 September 2014 03:27, Thomas Goirand wrote:
> I think we should all focus first on the Python Team modules, and see
> where that leads us.
Yes, that seems sensible to me. As well as any other packages we might
discover that cause breakage when testing Python Team modules with Django
1.7 (
On 12 September 2014 12:10, Brian May
wrote:
> Bugs with no response from Debian maintainer (except #755645 with no
> recent activity):
>
[...]
> #760875 [i| | ] [src:django-longerusername] django-longerusername:
> Please fix the package for Django 1.7
>
Possibly this bug should have gone i
On Fri, Sep 12, 2014 at 4:10 AM, Brian May
wrote:
> Obviously this is likely to fall out of date quickly. Apologies for any
> errors.
>
> I just wanted to try classify what is holding these bugs up.
>
>
> Bugs waiting for new Debian package:
>
> #755607 [i|+| ] [src:django-restricted-resource]
>
Hi Brian,
Thanks a lot for all of your work. I think it's a very important work if
we want Django 1.7.
I think we should all focus first on the Python Team modules, and see
where that leads us. Also, to me, considering the amount of remaining
bugs without a single reply, it's too early to upload
On Sep 12, 2014, at 08:18 AM, Jonas Genannt wrote:
>I: pybuild base:170: python2.7 setup.py test
>running test
>Searching for tox
>Reading https://pypi.python.org/simple/tox/
>Download error on https://pypi.python.org/simple/tox/: [Errno 111]
>Connection refused -- Some packages may not be found!
5 matches
Mail list logo