Bug#1016090: python-django breaks lots of autopkgtests

 > > On Aug 1, 2022, at 12:33 PM, Chris Lamb wrote: > Hmpf, this is deeply unfortunate. I was working under the incorrect > belief that the 4.0.x series was now the LTS branch. A number of > things encouraged this interpretation, including that the 4.0.x and > 4.1.x were the release streams

Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)

Stephan Sürken wrote: > Let's see if I got this right: > > django-registration is actually no longer discontinued, and now lives at > > https://github.com/ubernostrum/django-registration > > The (incompatible) *-redux fork lives at > > https://github.com/macropin/django-registration Yes.

Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)

Stephan Sürken wrote: >> As for p-d-r in general: Has there been any discussion here already >> if/how to package 'p-d-r-redux' (which seems to be a (still maintained) >> fork)? > > As we now have #806182, I am hoping for some discussion/advice there how > to exactly handle this in the future (I

Bug#806182: Upstream discontinued, replace with -redux

Actually, upstream is here: https://github.com/ubernostrum/django-registration martin f krafft wrote: > Package: python-django-registration > Version: 1.0+dfsg-2 > Severity: important > > This project has been discontinued: > > https://bitbucket.org/ubernostrum/django-registration/wiki/Home

Bug#797208: Does not work with django 1.8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FYI: a new (1.7, 1.8 and 1.9-compatible) release from upstream is likely to occur on Thursday 19 November :) Chris Lamb wrote: > severity 797208 serious thanks > > Hi, > >> Does not work with django 1.8 > > This is actually causing a FTBFS in

Bug#683364: New release coming

As a heads-up: a bug affecting Python 2.4 compatibility was found in the 1.3.2 package, and we will be issuing a 1.3.3 release based on that. The relevant commit is visible here: https://github.com/django/django/commit/d0d5dc6cd76f01c8a71b677357ad2f702cb54416 And the 1.3.3 release will likely

Bug#641405: several Django security issues

support anything older than that. That means we no longer support 1.1 or earlier versions in any official way. I'm quite certain that at least some of the security issues (especially the URLField problems) are present in 1.1. - -- James Bennett ja...@b-list.org -BEGIN PGP SIGNATURE

Bug#555419: python-django: embedded copies of Python modules: doctest, decimal

. - -- James Bennett ja...@b-list.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr43o4ACgkQNoTAwIyLKuHlywCgk7/40J6kSVNsZesW4Qor5pwh 1/sAoICZBWg6dBmW//EkYsBIkMiBQEcl =OkUe -END PGP SIGNATURE

Bug#527492: python-django: FTBFS: Could not import extension djangodocs

-- James Bennett ja...@b-list.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#505783: New upstream version available

*are* going to bump to 1.0.2 and re-roll, with a package due on Tuesday: http://groups.google.com/group/django-developers/msg/b32f923a257c0ee4 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#481164: Bad tarball for Django 0.96.2

that stuff in. I can't really go back and tweak that for something that isn't really a security fix, but an svn export from the 0.96-bugfixes branch in the Django repo should get you want you want, after which it's easy enough to make the tarball manually. -- James Bennett [EMAIL PROTECTED

Bug#450913: bash completion script breaks normal file completion

://code.djangoproject.com/ticket/6661 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#450913: bash completion script breaks normal file completion

This has been fixed upstream in Django trunk, as changeset 7156[1]. [1] http://code.djangoproject.com/changeset/7156 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#436983: python-django: pydoc django.db blows up

to *use* Django, but I believe this deals with the cases where we inadvertently made pydoc explode. [1] http://code.djangoproject.com/changeset/6832 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Bug#436983: python-django: pydoc django.db blows up

Brett Parker wrote: Hmmm. Yes, it's central, but a lot of the rest of it works with pydoc - I can see why this particular use case doesn't, but I'll take a looksee tomorrow incase there is an easy solution (I don't think there is, I think Raphael is spot on...) There isn't really an easy

Bug#407521: Security fix for Django auth system

to be logged in as someone else. This was fixed in revision 3754 of Django trunk[1], and that changeset applies cleanly to stock Django 0.95. [1] http://code.djangoproject.com/changeset/3754 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#407519: Security fix for Django i18n system

that arbitrary commands could be executed as a result of maliciously-named .po files. This was fixed in revision 3592 of Django trunk[1], and that changeset applies cleanly to stock Django 0.95. http://code.djangoproject.com/changeset/3592 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE

Bug#407607: Minor fix for Django FastCGI handling

. This was fixed in revision 4170 of Django trunk, and a patch which applies cleanly to stock Django 0.95 is in Django's 0.95-bugfixes branch (which tracks post-release updates and fixes for the 0.95 release): http://code.djangoproject.com/changeset/4363 -- James Bennett [EMAIL PROTECTED