On Tue, 23 May 2017, Scott Kitterman wrote: > > > On May 23, 2017 5:28:04 PM EDT, Alexander Wirt <[email protected]> wrote: > >On Tue, 23 May 2017, Raphael Hertzog wrote: > > > >> (please cc me on answers) > >> > >> On Tue, 23 May 2017, Debian FTP Masters wrote: > >> > please take the version from testing, not a version that never was > >in the archive > >> > >> I have been maintaining the 1.8.x LTS version of Django in > >jessie-backports since > >> December 2015. > >> > >> Except the very first, none of the 1.8.x versions that I uploaded in > >> jessie-backports have been in testing. > >> > >> Please let me continue providing this service to our users. > >> > >> Why are you suddenly acting on this upload and not the formers? > >You didn't followed the often stated policy. Full stop. We just never > >noticed. > > > >We stated that several times and you just decided that policy does not > >count > >for you. I think that is pretty unfair. > > There are security fixes in this upload. What's the way to get those fixed? > Backporting 1.10 isn't an option because it is incompatible with many other > packages. > > Would cherry-picked security fixes be okay? The policy is pretty clear. Backporting 1.10 and backport the other packages too.
It is maybe a problem and maybe we should get the policy changed - I personally don't think too. I don't wan't software that isn't in testing in backports - but doing it behinds our back is not an option. Alex _______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
