>
> 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 that
-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 sid
o it (1.2) gets
only security. We don't 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
--
James Bennett
ja...@b-list.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
x27;t pull 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
5 matches
Mail list logo
