Accepting request 1254138 from devel:languages:python:django

OBS-URL: https://build.opensuse.org/request/show/1254138
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-Django?expand=0&rev=127
This commit is contained in:
2025-03-20 18:24:28 +00:00
committed by Git OBS Bridge
6 changed files with 85 additions and 71 deletions

View File

@@ -1,67 +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 5.1.6, released February 5, 2025.
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 ``2EE82A8D9470983E`` 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 2EE82A8D9470983E
or via the GitHub API:
curl https://github.com/nessita.gpg | gpg --import -
Once the key is imported, verify this file:
gpg --verify Django-5.1.6.checksum.txt
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/5.1/Django-5.1.6.tar.gz
https://www.djangoproject.com/m/releases/5.1/Django-5.1.6-py3-none-any.whl
MD5 checksums
=============
39585ffad0b04e7d5d7726a6b4e45d41 Django-5.1.6.tar.gz
27ad2093eaef2c1aeb76cb8025cbbbf5 Django-5.1.6-py3-none-any.whl
SHA1 checksums
==============
c96db1b845d9f3a0982c6297f5cd78c43b3280d2 Django-5.1.6.tar.gz
70a0ffed34bb16e4373f95e91018bde4d0ef1b2f Django-5.1.6-py3-none-any.whl
SHA256 checksums
================
1e39eafdd1b185e761d9fab7a9f0b9fa00af1b37b25ad980a8aa0dac13535690 Django-5.1.6.tar.gz
8d203400bc2952fbfb287c2bbda630297d654920c72a73cc82a9ad7926feaad5 Django-5.1.6-py3-none-any.whl
-----BEGIN PGP SIGNATURE-----
iQJcBAEBCABGFiEEW1sboQ2FrHxcduOPLugqjZRwmD4FAmejcjsoHDEyNDMwNCtu
ZXNzaXRhQHVzZXJzLm5vcmVwbHkuZ2l0aHViLmNvbQAKCRAu6CqNlHCYPuO7D/9i
NqPgKoFDRpo47uqA7791xrWGspAlk1AXtaqdoGDWK0fyb6tetELAB05gICoAZk1q
3BN5qTU22dftpn6k26Vt3b16myrBUb3samncQ1z4DHWctnFUrTSs0ztkqc55w/SE
E2klPzON/D/4PBTfOPAq+1rXk9r/EVMmv6s9pOrgvr+Xjo+OiWshoBXVPxmTRws5
Sv3Ll1a/ifMg22bN5bgMBuY03UdFbXA4a52DvEmA3DC56EaRZsqzFbzlvldYYUgi
7Fy3u8fl1Gpl1XYTggnIcOogltAUeRomj5i5xo+Ge5Em8pI/F5EtuHH7zWL+2VDK
NyjYSSB9hY5dzJmGSTdv6yf+JtMNgG5n2fd2786Qcb5/NhtVjEMQPWMKiLZaCIZ6
5Y33gEmMCKXekaOk60PwwMZaqEQMirNcnSNEzOX2yjP/VIPixcQKm9iDhVg91t8G
UZVhsDV+1KrHseV+byMeXmHPHBx4WOi0+X5deU71aZn4NZSUmIyfMIDpag/B9Wis
OJZ7BNaUJXNl1JS9A2gxt8Kt3S6xZUdPbFXYXvpniuKOSBFl397oaqOtGPoP63Fw
QSnyExHibH57k7tq43hw04hLLMBEghhHA7TvYZrtoF10E/xEKJIflOAoicejYFmm
0UNCpq6lznK36fLJaA6cnuBYqJftKOSmVbMHOeQ7vw==
=mt6z
-----END PGP SIGNATURE-----

View File

@@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1e39eafdd1b185e761d9fab7a9f0b9fa00af1b37b25ad980a8aa0dac13535690
size 10700620

65
Django-5.1.7.checksum.txt Normal file
View File

@@ -0,0 +1,65 @@
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
This file contains MD5, SHA1, and SHA256 checksums for the source-code
tarball and wheel files of Django 5.1.7, released March 6, 2025.
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 ``3955B19851EA96EF`` 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 3955B19851EA96EF
or via the GitHub API:
curl https://github.com/sarahboyce.gpg | gpg --import -
Once the key is imported, verify this file:
gpg --verify Django-5.1.7.checksum.txt
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/5.1/Django-5.1.7-py3-none-any.whl
https://www.djangoproject.com/m/releases/5.1/Django-5.1.7.tar.gz
MD5 checksums
=============
bf291218572733211f4f41fab183d2e4 Django-5.1.7-py3-none-any.whl
be16b25fb0dc357e756668078a400f95 Django-5.1.7.tar.gz
SHA1 checksums
==============
e5d18f470b91eb56f0a50ce1573348a69bc944d6 Django-5.1.7-py3-none-any.whl
f17baedab00f847150a096d9593e532d3e840189 Django-5.1.7.tar.gz
SHA256 checksums
================
1323617cb624add820cb9611cdcc788312d250824f92ca6048fda8625514af2b Django-5.1.7-py3-none-any.whl
30de4ee43a98e5d3da36a9002f287ff400b43ca51791920bfb35f6917bfe041c Django-5.1.7.tar.gz
-----BEGIN PGP SIGNATURE-----
iQHhBAEBCABLFiEE6xs4DYrFLQArrNMyOVWxmFHqlu8FAmfJYWwtHDQyMjk2NTY2
K3NhcmFoYm95Y2VAdXNlcnMubm9yZXBseS5naXRodWIuY29tAAoJEDlVsZhR6pbv
xIcL/iwdZbuF3MOzTRNPNDo1P+MztLL2E7ralnLklcneDoEuNPx3iTyeOycBu5c5
PWluzQIASnnnUsTnwm2yBka8ogqgdOh1jxXy+Kvfe15qfWA5UkkiMpjnAHY14/Uh
9Ibb2wr44J3LU5Y1+7MQweq50M3dAjVGSnqxTO8zuW7LJsQGsVfgkhXgVd+/pgkx
XR29jXZtBAX21yObIsjK6Rw52VGZYDfFcIZ13MjexlorR+F5sIZWnPPykMyxhIRE
mn4V1ompDAywJyg6eFmPgpogiPU3WEu8zImDHPcw7DbTXTbMzwmdFrLzJQHpZqmn
GD3FGC9Vp76o2b21sJrn1s7uw8/cfUp+NoCvIeYQc+SKuLDDtgKX0O9J1yWEi74H
LFuWdSxXosLCpHP9hq6h8uNXesaMy0tbKEK9+PE718OmGapmZgFtXmDVCha235gM
BE6hS+A4+ERH/9GAw3TgbAaf8NAT8Eere2Pmn7pjCOw9Nbtne9dEq91ytGJwYzod
jl5+cA==
=OdRx
-----END PGP SIGNATURE-----

3
Django-5.1.7.tar.gz Normal file
View File

@@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:30de4ee43a98e5d3da36a9002f287ff400b43ca51791920bfb35f6917bfe041c
size 10716510

View File

@@ -1,3 +1,19 @@
-------------------------------------------------------------------
Tue Mar 18 13:01:55 UTC 2025 - Markéta Machová <mmachova@suse.com>
- Update to 5.1.7 (bsc#1239052)
* CVE-2025-26699: Potential denial-of-service vulnerability in
django.utils.text.wrap()
* Fixed a bug in Django 5.1 where the {% querystring %} template tag
returned an empty string rather than "?"
* Fixed a bug in Django 5.1 where FileSystemStorage, with allow_overwrite
set to True, did not truncate the overwritten file content
* Fixed a regression in Django 5.1 where the count and exists methods of
ManyToManyField related managers would always return 0 and False when
the intermediary model back references used to_field
* Fixed a regression in Django 5.1 where the pre_save and post_save signals
for LogEntry were not sent when deleting a single object in the admin
-------------------------------------------------------------------
Tue Feb 11 12:52:16 UTC 2025 - Markéta Machová <mmachova@suse.com>

View File

@@ -21,7 +21,7 @@
%bcond_with memcached
%{?sle15_python_module_pythons}
Name: python-Django
Version: 5.1.6
Version: 5.1.7
Release: 0
Summary: A high-level Python Web framework
License: BSD-3-Clause