diff --git a/Django-1.9.6.tar.gz b/Django-1.9.6.tar.gz deleted file mode 100644 index fb2b1f8..0000000 --- a/Django-1.9.6.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e5a1d1a831c06475c708126c6a7e0ae0e67adac9d8a7c39cf0695ad79030b9d9 -size 7441794 diff --git a/Django-1.9.6.tar.gz.asc b/Django-1.9.6.tar.gz.asc deleted file mode 100644 index 0ee5b38..0000000 --- a/Django-1.9.6.tar.gz.asc +++ /dev/null @@ -1,63 +0,0 @@ ------BEGIN PGP SIGNED MESSAGE----- -Hash: SHA256 - -This file contains MD5, SHA1, and SHA256 checksums for the source-code -tarball and wheel files of Django 1.9.6, released May 2, 2016. - -To use this file, you will need a working install of PGP or other -compatible public-key encryption software. You will also need to have -the Django release manager's public key in your keyring; this key has -the ID ``1E8ABDC773EDE252`` and can be imported from the MIT -keyserver. For example, if using the open-source GNU Privacy Guard -implementation of PGP: - - gpg --keyserver pgp.mit.edu --recv-key 1E8ABDC773EDE252 - -Once the key is imported, verify this file:: - - gpg --verify <> - -Once you have verified this file, you can use normal MD5, SHA1, or SHA256 -checksumming applications to generate the checksums of the Django -package and compare them to the checksums listed below. - -Release packages: -================= - -https://www.djangoproject.com/m/releases/1.9/Django-1.9.6.tar.gz -https://www.djangoproject.com/m/releases/1.9/Django-1.9.6-py2.py3-none-any.whl - -MD5 checksums: -============== - -70687b2d4a2dfa51f70407a3ce2abcbb Django-1.9.6-py2.py3-none-any.whl -07d9b3883198caa847b917c94b665452 Django-1.9.6.tar.gz - -SHA1 checksums: -=============== - -e5921b0c7eff6ea9154c9a9637c452eb3c88c81f Django-1.9.6-py2.py3-none-any.whl -1c4c60203fea0e82837bb7f39d008c131aba6167 Django-1.9.6.tar.gz - -SHA256 checksums: -================= - -83f234f52a86eb983de3616b8ff3b0368e4da1d975fa5449b08588b749e7946c Django-1.9.6-py2.py3-none-any.whl -e5a1d1a831c06475c708126c6a7e0ae0e67adac9d8a7c39cf0695ad79030b9d9 Django-1.9.6.tar.gz ------BEGIN PGP SIGNATURE----- -Version: GnuPG v1 - -iQIcBAEBCAAGBQJXJ9NNAAoJEB6Kvcdz7eJSI6YP/iNICr48zDoDgK6J7il4BXJE -+dkprnXzqZHt329A+dZEceat7FtdWi8UzuR7/WkbVXIyOZT7jy6VBNJWVZz722ht -HwwTi81KuiuWMvHPrsB74+QHpBAaS4wWSdmitK2sP1loMAURPXSNy1ZNHdWxvper -8wisWIVnwqV6fmLvmJYooJ/8bgftpjDBbiLB7xMQe/qnqiOD8gh1zY8F8DAY+Fwu -KrL2auLJ7Yk0kTa65YSR/FNxh9oMT1wxxdE5hCTdM6YUJQVTE2mF1LloBcdV28mX -cRmsVr+e7kWtJ+AqeyOcEOy/bnn7e6r56//1y3c6TeWXDfF7RgRvMwz/YtfheQ+G -Dn9HqW4zMtH4azgjlxg1PG9vMh4TBUeEJ53tPVGOuvYIevwogzeqpgCngP2AhYJ0 -nec37GNaKjSxlDRPImex8EpAMaIL7athiVt50Dy8rYXVe+dSQ0d3vGBOKPShtXJ4 -shoRf+M3uM/B2nxwuBD80gh50EYxo+PVVzzsgBj2bOdzXYcnzOYnyn2tMhaOKDbQ -a8MFSDGDGmhWRLKMXQVpO001Rx7hQF+FDT1kYDRVXr5j3nZ4oRgNhQL9T9bepwMe -msMMpRsb3DNDcx5gF9fjq4gVfBeEPCtyPP/nFSgsZNufqrsJQL9GM/EdESDXZXbp -ko7nv9ODlFVvo+ffMGTv -=yPA8 ------END PGP SIGNATURE----- diff --git a/Django-1.9.9.tar.gz b/Django-1.9.9.tar.gz new file mode 100644 index 0000000..a895f02 --- /dev/null +++ b/Django-1.9.9.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e340fb9d534aeb543280e46c3b85e6e1049029a4e6ba5571375b11c914bfde8c +size 7493187 diff --git a/Django-1.9.9.tar.gz.asc b/Django-1.9.9.tar.gz.asc new file mode 100644 index 0000000..0ca788d --- /dev/null +++ b/Django-1.9.9.tar.gz.asc @@ -0,0 +1,63 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA256 + +This file contains MD5, SHA1, and SHA256 checksums for the source-code +tarball and wheel files of Django 1.9.9, released August 1, 2016. + +To use this file, you will need a working install of PGP or other +compatible public-key encryption software. You will also need to have +the Django release manager's public key in your keyring; this key has +the ID ``1E8ABDC773EDE252`` and can be imported from the MIT +keyserver. For example, if using the open-source GNU Privacy Guard +implementation of PGP: + + gpg --keyserver pgp.mit.edu --recv-key 1E8ABDC773EDE252 + +Once the key is imported, verify this file:: + + gpg --verify <> + +Once you have verified this file, you can use normal MD5, SHA1, or SHA256 +checksumming applications to generate the checksums of the Django +package and compare them to the checksums listed below. + +Release packages: +================= + +https://www.djangoproject.com/m/releases/1.9/Django-1.9.9.tar.gz +https://www.djangoproject.com/m/releases/1.9/Django-1.9.9-py2.py3-none-any.whl + +MD5 checksums: +============== + +22a7b6ebd216b3bfe2f7c25525ecd444 Django-1.9.9-py2.py3-none-any.whl +af2e5f02b72400ddaef7f923a7fda6a9 Django-1.9.9.tar.gz + +SHA1 checksums: +=============== + +521ac4aa251b9378832bde597047c69126c6dfab Django-1.9.9-py2.py3-none-any.whl +2f971cfb115681cb30be5d9496a6e3f3369679cd Django-1.9.9.tar.gz + +SHA256 checksums: +================= + +3236d2292d6ef6afbda0226c255a7901d271ae86d14768bb20e1b6864c66f7e6 Django-1.9.9-py2.py3-none-any.whl +e340fb9d534aeb543280e46c3b85e6e1049029a4e6ba5571375b11c914bfde8c Django-1.9.9.tar.gz +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1 + +iQIcBAEBCAAGBQJXn48xAAoJEB6Kvcdz7eJSfaMQAJqzD1D1SBr5qmbLn3rhkmyW +62hZkBXeqDcl/tyeYQFADXWjjqXPJKDjJXx9bku0HDFeVthmEgcl8k34H68Z7pxU +HdyjDVn/EVHUT8Hu+6e2IrGypO3D4gKiYFRvJyJ64+l6uIikP0hvOi4Jte8adT+/ +T2kyOKzRk05KDaAeuT5IQPYHiWawTOG3W9mJMEnE9NlsJEJUJo3xdqDK+oG6yif0 +BHM1XKqOtmSKAeVExTYv6JAB9jm+agNwCdsbWkGijtLmTkUvksvI7Umlr4B6H9s3 +dyDncXgiNMcjp1l2fnQMqHmT5UqaEoo2+qUz0Q70/rRpMgPvmqBPUbD5IEoGj0Dd +GZaMbvOES2qXyh5IZ9yYftNZ7dIJBGp23xnxY6Y3xCPkabAJTFKnn/jwWLmQqM6r +MuAwl0OBwvoqfymnFJbDr0ww/pEdH16LAR8unUnDBg/9BNFJu/DoiAfs+qFc38qv +YPK6vNq2TWrGD4L01rkn1A8O9ib9tO405m6jXXMzcke6IW2j37t2BtUlEJxMsB+k +btdLr7HIt7g5PNZiT/iJukOaJrPtksdx98pmCAAj+WXBFG/3OANbzFEbY6M4NBUE +OvsQCOLNfWl3Itw9vT9zM52nUlJBmQ3z4jXOTPC//qnrOYOlYmJKZ9g+0gyKzbZT +9eyNrwnAQdRzpiexoo6V +=hyrv +-----END PGP SIGNATURE----- diff --git a/python-Django.changes b/python-Django.changes index 6195403..169904e 100644 --- a/python-Django.changes +++ b/python-Django.changes @@ -1,3 +1,44 @@ +------------------------------------------------------------------- +Tue Aug 9 09:11:24 UTC 2016 - aplanas@suse.com + +- Update to 1.9.9 + Bugfixes + * Fixed invalid HTML in template postmortem on the debug page + (#26938). + * Fixed some GIS database function crashes on MySQL 5.7 (#26657). + +- Update to 1.9.8 + Fix XSS in admin’s add/change related popup (bsc#988420) + Unsafe usage of JavaScript’s Element.innerHTML could result in XSS + in the admin’s add/change related popup. Element.textContent is now + used to prevent execution of the data. + The debug view also used innerHTML. Although a security issue wasn’t + identified there, out of an abundance of caution it’s also updated + to use textContent. + + Bugfixes + * Fixed missing varchar/text_pattern_ops index on CharField and + TextField respectively when using AddField on PostgreSQL (#26889). + * Fixed makemessages crash on Python 2 with non-ASCII file names + (#26897). + +- Update to 1.9.7 + Bugfixes + * Removed the need for the request context processor on the admin + login page to fix a regression in 1.9 (#26558). + * Fixed translation of password validators’ help_text in forms + (#26544). + * Fixed a regression causing the cached template loader to crash + when using lazy template names (#26603). + * Fixed on_commit callbacks execution order when callbacks make + transactions (#26627). + * Fixed HStoreField to raise a ValidationError instead of crashing + on non-dictionary JSON input (#26672). + * Fixed dbshell crash on PostgreSQL with an empty database name + (#26698). + * Fixed a regression in queries on a OneToOneField that has to_field + and primary_key=True (#26667). + ------------------------------------------------------------------- Tue May 3 08:23:48 UTC 2016 - aplanas@suse.com diff --git a/python-Django.spec b/python-Django.spec index 50e8409..495cdf5 100644 --- a/python-Django.spec +++ b/python-Django.spec @@ -17,7 +17,7 @@ Name: python-Django -Version: 1.9.6 +Version: 1.9.9 Release: 0 Summary: A high-level Python Web framework License: BSD-3-Clause