python-django - Debian Package Tracker

general

source: python-django (main)
version: 3:5.2.17-1
maintainer: Debian Python Team (DMD)
uploaders: Brian May [DMD] – Chris Lamb [DMD] – Raphaël Hertzog [DMD] – Luke Faraone [DMD]
arch: all
std-ver: 4.7.4
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2:2.2.28-1~deb11u2
o-o-sec: 2:2.2.28-1~deb11u12
oldstable: 3:3.2.25-0+deb12u3
old-sec: 3:3.2.25-0+deb12u2
old-bpo: 3:4.2.21-1~bpo12+1
old-p-u: 3:3.2.25-0+deb12u3
stable: 3:4.2.28-0+deb13u2
stable-sec: 3:4.2.28-0+deb13u1
stable-bpo: 3:5.2.16-1~bpo13+1
testing: 3:5.2.16-1
unstable: 3:5.2.17-1
exp: 3:6.1~rc1-1

versioned links

2:2.2.28-1~deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:2.2.28-1~deb11u12: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:3.2.25-0+deb12u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:3.2.25-0+deb12u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:4.2.21-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:4.2.28-0+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:4.2.28-0+deb13u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:5.2.16-1~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:5.2.16-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:5.2.17-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:6.0.4-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:6.1~rc1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python-django-doc
python3-django (2 bugs: 0, 2, 0, 0)

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

https://salsa.debian.org/api/v4/projects/python-team%2Fpackages%2Fpython-django API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.

Created: 2022-08-03 Last update: 2026-08-06 02:33

Debci reports failed tests high

unstable: pass (log)
The tests ran in 0:11:43
Last run: 2026-07-07T02:09:18.000Z
Previous status: unknown

testing: pass (log)
The tests ran in 0:13:12
Last run: 2026-07-28T11:35:34.000Z
Previous status: unknown

stable: fail (log)
The tests ran in 0:02:13
Last run: 2026-07-07T09:18:28.000Z
Previous status: unknown

Created: 2026-03-17 Last update: 2026-08-06 01:30

21 security issues in trixie high

There are 21 open security issues in trixie.

4 important issues:

CVE-2026-15307: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.
CVE-2026-15337: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Jaeyoung Jang for reporting this issue.
CVE-2026-15830: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
CVE-2026-15920: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.

17 issues left for the package maintainer to handle:

CVE-2026-3902: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
CVE-2026-4277: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank N05ec@LZU-DSLab for reporting this issue.
CVE-2026-4292: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using `ModelAdmin.list_editable` incorrectly allowed new instances to be created via forged `POST` data. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.
CVE-2026-5766: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. ASGI requests with a missing or understated `Content-Length` header can bypass the `FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading large files into memory and causing service degradation. As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on `FILE_UPLOAD_MAX_MEMORY_SIZE`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kyle Agronick for reporting this issue.
CVE-2026-6873: (needs triaging) An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.http.HttpRequest.get_signed_cookie` in Django uses a non-injective salt derivation (concatenating the cookie name and salt argument), which allows a remote attacker to use a cookie in a context different from the one where it was signed, via distinct `(name, salt)` pairs that produce the same concatenation. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Peng Zhou for reporting this issue.
CVE-2026-6907: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. `django.middleware.cache.UpdateCacheMiddleware` erroneously caches requests where the `Vary` header contained an asterisk (`'*'`). This can lead to private data being stored and served. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmad Sadeddin for reporting this issue.
CVE-2026-7666: (needs triaging) An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.core.mail.backends.smtp.EmailBackend` in Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake when `fail_silently=True`, which allows on-path network attackers to read email content via cleartext interception. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kasper Dupont for reporting this issue.
CVE-2026-8404: (needs triaging) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmed Badawe for reporting this issue.
CVE-2026-25674: (needs triaging) An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Race condition in file-system storage and file-based cache backends in Django allows an attacker to cause file system objects to be created with incorrect permissions via concurrent requests, where one thread's temporary `umask` change affects other threads in multi-threaded environments. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
CVE-2026-33033: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allows remote attackers to degrade performance by submitting multipart uploads with `Content-Transfer-Encoding: base64` including excessive whitespace. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Seokchan Yoon for reporting this issue.
CVE-2026-33034: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Superior for reporting this issue.
CVE-2026-35192: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.
CVE-2026-35193: (needs triaging) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Shai Berger for reporting this issue.
CVE-2026-48587: (needs triaging) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.utils.cache.has_vary_header()` in Django does not strip leading or trailing whitespace from `Vary` response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Navid Rezazadeh for reporting this issue.
CVE-2026-48588: (needs triaging) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote attackers to read private data from the shared cache. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Chris Whyland for reporting this issue.
CVE-2026-53877: (needs triaging) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `django.contrib.gis.gdal.GDALRaster` over-reads its in-memory buffer when constructed from a bytes object, which can disclose adjacent memory or cause service degradation via a potential segmentation fault when the `vsi_buffer` property is accessed. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy for reporting this issue.
CVE-2026-53878: (needs triaging) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `DomainNameValidator` does not prohibit newlines in domain names (unless used via a form field, since `CharField` strips newlines). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because `HttpResponse` prohibits newlines in HTTP headers. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy for reporting this issue.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-03-03 Last update: 2026-08-05 07:02

4 security issues in forky high

There are 4 open security issues in forky.

4 important issues:

CVE-2026-15307: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.
CVE-2026-15337: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Jaeyoung Jang for reporting this issue.
CVE-2026-15830: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
CVE-2026-15920: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.

Created: 2026-08-04 Last update: 2026-08-05 07:02

23 security issues in bullseye high

There are 23 open security issues in bullseye.

4 important issues:

CVE-2026-15307: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.
CVE-2026-15337: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Jaeyoung Jang for reporting this issue.
CVE-2026-15830: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
CVE-2026-15920: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.

16 issues postponed or untriaged:

CVE-2026-3902: (postponed; to be fixed through a stable update) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
CVE-2026-4277: (postponed; to be fixed through a stable update) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank N05ec@LZU-DSLab for reporting this issue.
CVE-2026-4292: (postponed; to be fixed through a stable update) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using `ModelAdmin.list_editable` incorrectly allowed new instances to be created via forged `POST` data. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.
CVE-2026-5766: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. ASGI requests with a missing or understated `Content-Length` header can bypass the `FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading large files into memory and causing service degradation. As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on `FILE_UPLOAD_MAX_MEMORY_SIZE`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kyle Agronick for reporting this issue.
CVE-2026-6873: (postponed; to be fixed through a stable update) An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.http.HttpRequest.get_signed_cookie` in Django uses a non-injective salt derivation (concatenating the cookie name and salt argument), which allows a remote attacker to use a cookie in a context different from the one where it was signed, via distinct `(name, salt)` pairs that produce the same concatenation. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Peng Zhou for reporting this issue.
CVE-2026-6907: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. `django.middleware.cache.UpdateCacheMiddleware` erroneously caches requests where the `Vary` header contained an asterisk (`'*'`). This can lead to private data being stored and served. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmad Sadeddin for reporting this issue.
CVE-2026-7666: (postponed; to be fixed through a stable update) An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.core.mail.backends.smtp.EmailBackend` in Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake when `fail_silently=True`, which allows on-path network attackers to read email content via cleartext interception. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kasper Dupont for reporting this issue.
CVE-2026-8404: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmed Badawe for reporting this issue.
CVE-2026-25674: (postponed; to be fixed through a stable update) An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Race condition in file-system storage and file-based cache backends in Django allows an attacker to cause file system objects to be created with incorrect permissions via concurrent requests, where one thread's temporary `umask` change affects other threads in multi-threaded environments. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
CVE-2026-33033: (postponed; to be fixed through a stable update) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allows remote attackers to degrade performance by submitting multipart uploads with `Content-Transfer-Encoding: base64` including excessive whitespace. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Seokchan Yoon for reporting this issue.
CVE-2026-33034: (postponed; to be fixed through a stable update) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Superior for reporting this issue.
CVE-2026-35192: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.
CVE-2026-35193: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Shai Berger for reporting this issue.
CVE-2026-48587: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.utils.cache.has_vary_header()` in Django does not strip leading or trailing whitespace from `Vary` response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Navid Rezazadeh for reporting this issue.
CVE-2026-48588: (postponed; to be fixed through a stable update) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote attackers to read private data from the shared cache. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Chris Whyland for reporting this issue.
CVE-2026-53877: (postponed; to be fixed through a stable update) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `django.contrib.gis.gdal.GDALRaster` over-reads its in-memory buffer when constructed from a bytes object, which can disclose adjacent memory or cause service degradation via a potential segmentation fault when the `vsi_buffer` property is accessed. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy for reporting this issue.

3 ignored issues:

CVE-2024-38875: An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.
CVE-2024-41990: An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2024-45230: An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.

Created: 2026-08-04 Last update: 2026-08-05 07:02

23 security issues in bookworm high

There are 23 open security issues in bookworm.

4 important issues:

CVE-2026-15307: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.
CVE-2026-15337: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Jaeyoung Jang for reporting this issue.
CVE-2026-15830: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
CVE-2026-15920: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.

19 issues postponed or untriaged:

CVE-2026-3902: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
CVE-2026-4277: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank N05ec@LZU-DSLab for reporting this issue.
CVE-2026-4292: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using `ModelAdmin.list_editable` incorrectly allowed new instances to be created via forged `POST` data. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.
CVE-2026-5766: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. ASGI requests with a missing or understated `Content-Length` header can bypass the `FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading large files into memory and causing service degradation. As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on `FILE_UPLOAD_MAX_MEMORY_SIZE`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kyle Agronick for reporting this issue.
CVE-2026-6873: (needs triaging) An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.http.HttpRequest.get_signed_cookie` in Django uses a non-injective salt derivation (concatenating the cookie name and salt argument), which allows a remote attacker to use a cookie in a context different from the one where it was signed, via distinct `(name, salt)` pairs that produce the same concatenation. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Peng Zhou for reporting this issue.
CVE-2026-6907: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. `django.middleware.cache.UpdateCacheMiddleware` erroneously caches requests where the `Vary` header contained an asterisk (`'*'`). This can lead to private data being stored and served. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmad Sadeddin for reporting this issue.
CVE-2026-7666: (needs triaging) An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.core.mail.backends.smtp.EmailBackend` in Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake when `fail_silently=True`, which allows on-path network attackers to read email content via cleartext interception. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kasper Dupont for reporting this issue.
CVE-2026-8404: (needs triaging) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmed Badawe for reporting this issue.
CVE-2024-38875: (needs triaging) An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.
CVE-2024-41990: (needs triaging) An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2024-45230: (needs triaging) An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2026-25674: (needs triaging) An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Race condition in file-system storage and file-based cache backends in Django allows an attacker to cause file system objects to be created with incorrect permissions via concurrent requests, where one thread's temporary `umask` change affects other threads in multi-threaded environments. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
CVE-2026-33033: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allows remote attackers to degrade performance by submitting multipart uploads with `Content-Transfer-Encoding: base64` including excessive whitespace. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Seokchan Yoon for reporting this issue.
CVE-2026-33034: (needs triaging) An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Superior for reporting this issue.
CVE-2026-35192: (needs triaging) An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.
CVE-2026-35193: (needs triaging) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Shai Berger for reporting this issue.
CVE-2026-48587: (needs triaging) An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.utils.cache.has_vary_header()` in Django does not strip leading or trailing whitespace from `Vary` response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Navid Rezazadeh for reporting this issue.
CVE-2026-48588: (postponed; to be fixed through a stable update) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote attackers to read private data from the shared cache. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Chris Whyland for reporting this issue.
CVE-2026-53877: (postponed; to be fixed through a stable update) An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `django.contrib.gis.gdal.GDALRaster` over-reads its in-memory buffer when constructed from a bytes object, which can disclose adjacent memory or cause service degradation via a potential segmentation fault when the `vsi_buffer` property is accessed. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy for reporting this issue.

Created: 2026-08-04 Last update: 2026-08-05 07:02

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2026-03-12 Last update: 2026-08-06 03:05

Multiarch hinter reports 1 issue(s) low

There are issues with the multiarch metadata for this package.

python-django-doc could be marked Multi-Arch: foreign

Created: 2023-09-25 Last update: 2026-08-05 22:20

debian/patches: 2 patches to forward upstream low

Among the 6 debian patches available in version 3:5.2.17-1 of the package, we noticed the following issues:

2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2026-05-13 Last update: 2026-08-05 06:30

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2026-04-29 11:32

testing migrations

excuses:
- Migration status for python-django (3:5.2.16-1 to 3:5.2.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for beanbag-docutils/2.4-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for debugpy/1.8.20+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for debusine/0.15.0: amd64: Pass, arm64: Pass, armhf: Failed (not a regression) ♻ (reference ♻), i386: Pass, loong64: Test triggered, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for debusine/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for diskcache/5.6.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for dj-database-url/3.1.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for dj-static/0.0.6-8: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-allauth/65.15.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-anymail/15.0-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-assets/2.0-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-auditlog/3.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-auditlog/n/a: ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-auth-ldap/5.3.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-auto-one-to-one/3.3.6-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-auto-one-to-one/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-axes/5.39.0-9: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-bleach/3.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-cachalot/2.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-cache-memoize/0.2.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-cas-server/3.1.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-choices-field/4.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-classy-tags/4.1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-compression-middleware/0.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-cors-headers/4.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-countries/7.6.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-cte/3.0.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-cte/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-dbbackup/4.2.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-dirtyfields/1.3.1-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-downloadview/2.4.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-filter/25.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-fsm/2.8.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-fsm-2/4.2.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-fsm-admin/1.2.5-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-fsm-log/5.0.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-graphiql-debug-toolbar/0.2.0-8: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-guardian/2.4.0-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-haystack/3.3.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-historical-currencies/0.0.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-housekeeping/1.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-htmx/1.28.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-iconify/0.5.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-impersonate/1.9.2-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-invitations/2.1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-ipware/4.0.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-json-widget/2.1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-macaddress/1.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-mailman3/1.3.15-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-maintenancemode/0.11.7+git221001-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-markupfield/2.0.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-memoize/2.2.0+dfsg-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-model-utils/5.0.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-model-utils/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-modeltranslation/0.20.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-ninja/1.6.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-oauth-toolkit/3.3.0+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-organizations/2.3.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-phonenumber-field/8.4.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-picklefield/3.4.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-picklefield/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-pipeline/4.1.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-polymodels/1.8.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-polymorphic/4.10.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-prometheus: loong64: Test triggered
- ∙ ∙ Autopkgtest for django-prometheus/2.5.0-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-python3-ldap/0.15.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-q/1.10.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-q/n/a: ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-qr-code/4.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-ranged-response/0.2.0-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-recurrence/1.14-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-recurrence/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-redis/5.4.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-reversion/6.3.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-rich/2.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-sass-processor/1.4.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-sekizai/4.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-select2/7.10.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-session-security/2.6.7+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), s390x: Pass
- ∙ ∙ Autopkgtest for django-session-security/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for django-simple-captcha/0.7.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-sitetree/1.18.0+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-tables/3.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for django-taggit/6.1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-tastypie/0.15.1-2: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-uwsgi/1.1.2-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-webpack-loader/0.6.0-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for django-webtest/1.9.14-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for djangorestframework: loong64: Test triggered
- ∙ ∙ Autopkgtest for djangorestframework-filters/1.0.0.dev2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for djangorestframework-gis/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for djoser/2.3.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for drf-generators/0.5.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for factory-boy/3.3.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for freedombox/26.10: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for graphite-web/1.2.1~pre2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for horizon/3:25.7.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for hyperkitty/1.3.12-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), s390x: Pass
- ∙ ∙ Autopkgtest for hyperkitty/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for kombu/5.6.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for lava/2026.06-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for lazy-object-proxy/1.12.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for manila-ui/15.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for mistral-dashboard/22.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for ontospy/2.1.1~dfsg2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for postorius/1.3.13-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for postorius/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for pydevd/3.5.0+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for pygeofilter/0.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for pylint-django/2.6.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for pytest-django/4.12.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for pytest-django/n/a: ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-applicationinsights/0.11.10-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-authlib/1.7.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-crispy-bootstrap3/2024.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-crispy-bootstrap4/2025.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-crispy-bootstrap5/2025.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-cross-web/0.7.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-daphne/4.2.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django/3:5.2.17-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered (failure will be ignored), ppc64el: Ignored failure ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for python-django-adminplus/0.6-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-analytical/3.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-appconf/1.2.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-bootstrap-form/3.4-10: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-braces/1.17.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-cache-machine/1.2.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-celery-beat/2.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-celery-results/2.6.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-channels/4.3.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-colorfield/0.11.0+ds1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-compressor/4.5.1-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-constance/4.3.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-contact-form/5.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-contrib-comments/2.2.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-crispy-forms/2.6-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-crispy-forms-foundation/1.1.0+ds-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-crum/0.7.9-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-crum/n/a: ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-csp/3.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-dbconn-retry/0.3.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-debug-toolbar/1:7.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-dynamic-fixture/4.0.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-extensions/4.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-extra-views/0.14.0-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-formtools/2.5.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-gravatar2/1.4.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-guid/3.5.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-hashids/0.7.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-health-check/3.20.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-ical/1.9.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-imagekit/6.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), s390x: Pass
- ∙ ∙ Autopkgtest for python-django-imagekit/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-import-export/4.3.5-2.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-js-asset/4.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-libsass/0.9-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-modelcluster: loong64: Test triggered, riscv64: Test triggered
- ∙ ∙ Autopkgtest for python-django-money/3.6.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-money/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-mptt/0.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-navtag/3.3.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-netfields/1.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-object-actions/5.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-ordered-model/3.7.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-otp/1.7.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-parler/2.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-pgbulk/3.3.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-pgschemas/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-pgtransaction/2.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-pgtrigger/4.17.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-pgtrigger/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-postgres-extra/2.0.9-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-ratelimit/4.1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-rest-framework-guardian/0.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-rest-hooks/1.6.0-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-rules/3.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-simple-history/3.7.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-solo/2.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-split-settings/1.3.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-storages/1.14.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-structlog: loong64: Test triggered
- ∙ ∙ Autopkgtest for python-django-stubs/5.2.9-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for python-django-swapper/1.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-tagging/1:0.5.0-5.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-tasks/0.12.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-tasks-db/0.12.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-tasks-db/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-tasks-rq/0.12.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-test-migrations/1.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-timescaledb/0.2.13-4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for python-django-timezone-field: loong64: Test triggered, riscv64: Test triggered
- ∙ ∙ Autopkgtest for python-django-tree-queries/0.24-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-treebeard/5.0.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-waffle/4.2.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), s390x: Pass
- ∙ ∙ Autopkgtest for python-django-waffle/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-django-zeal/2.0.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-djangorestframework-flex-fields/1.0.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-djangorestframework-flex-fields/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-djangorestframework-simplejwt/5.5.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-djangorestframework-simplejwt/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-djangorestframework-yaml/3.0.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-djangosaml2/1.12.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-djangosaml2/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-drf-spectacular/0.28.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-enmerkar/0.7.1-8: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-hypothesis/6.152.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for python-json-log-formatter/1.1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-jsonrpc/1.13.0-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-livereload/2.7.1-0.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-livereload/n/a: ppc64el: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-lti/0.9.5-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-model-bakery/1.20.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-openapi-core/0.23.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-opentelemetry/1.43.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-pyfakefs/6.2.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-pytest-djangoapp/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-scrapy-djangoitem/1.1.1-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), s390x: Pass
- ∙ ∙ Autopkgtest for python-scrapy-djangoitem/n/a: riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-sparkpost/1.3.10-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-sphinxcontrib-django/2.5-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-testfixtures/11.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-twilio/9.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python-webargs/8.7.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-whitenoise/6.8.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-xapian-haystack/3.1.0-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for python-xapian-haystack/n/a: ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-xmlrunner/4.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for slm/3.3-2.1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ Autopkgtest for social-auth-app-django/6.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for trove-dashboard/26.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Lintian check waiting for test results - info
- ∙ ∙ Too young, only 1 of 2 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[rss feed]

[2026-08-06] Accepted python-django 3:6.1-1 (source) into experimental (Chris Lamb)
[2026-08-04] Accepted python-django 3:5.2.17-1 (source) into unstable (Chris Lamb)
[2026-07-22] Accepted python-django 3:6.1~rc1-1 (source) into experimental (Chris Lamb)
[2026-07-10] Accepted python-django 3:5.2.16-1~bpo13+1 (source all) into stable-backports (Chris Lamb)
[2026-07-10] python-django 3:5.2.16-1 MIGRATED to testing (Debian testing watch)
[2026-07-07] Accepted python-django 3:5.2.16-1 (source) into unstable (Chris Lamb)
[2026-06-27] Accepted python-django 3:5.2.15-2~bpo13+1 (source all) into stable-backports (Debian FTP Masters) (signed by: Chris Lamb)
[2026-06-25] python-django 3:5.2.15-2 MIGRATED to testing (Debian testing watch)
[2026-06-24] Accepted python-django 3:6.1~beta1-1 (source) into experimental (Chris Lamb)
[2026-06-08] Accepted python-django 3:5.2.15-2 (source) into unstable (Chris Lamb)
[2026-06-03] Accepted python-django 3:5.2.15-1 (source) into unstable (Chris Lamb)
[2026-06-03] Accepted python-django 3:6.0.6-1 (source) into experimental (Chris Lamb)
[2026-05-28] Accepted python-django 3:3.2.25-0+deb12u3 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2026-05-28] Accepted python-django 3:4.2.28-0+deb13u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2026-05-12] Accepted python-django 3:5.2.14-2 (source) into unstable (Chris Lamb)
[2026-05-05] Accepted python-django 3:5.2.14-1 (source) into unstable (Chris Lamb)
[2026-05-05] Accepted python-django 3:6.0.5-1 (source) into experimental (Chris Lamb)
[2026-04-28] Accepted python-django 3:5.2.13-1 (source) into unstable (Chris Lamb)
[2026-04-10] python-django 3:4.2.30-1 MIGRATED to testing (Debian testing watch)
[2026-04-07] Accepted python-django 3:4.2.30-1 (source) into unstable (Chris Lamb)
[2026-04-07] Accepted python-django 3:6.0.4-1 (source) into experimental (Chris Lamb)
[2026-03-09] python-django 3:4.2.29-1 MIGRATED to testing (Debian testing watch)
[2026-03-03] Accepted python-django 3:4.2.29-1 (source) into unstable (Chris Lamb)
[2026-03-03] Accepted python-django 3:6.0.3-1 (source) into experimental (Chris Lamb)
[2026-02-28] Accepted python-django 3:3.2.25-0+deb12u2 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2026-02-27] Accepted python-django 3:4.2.28-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2026-02-26] Accepted python-django 3:3.2.25-0+deb12u2 (source) into oldstable-security (Debian FTP Masters) (signed by: Chris Lamb)
[2026-02-26] Accepted python-django 3:4.2.28-0+deb13u1 (source) into stable-security (Debian FTP Masters) (signed by: Chris Lamb)
[2026-02-21] Accepted python-django 3:3.2.25-0+deb12u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2026-02-19] Accepted python-django 2:2.2.28-1~deb11u12 (source) into oldoldstable-security (Chris Lamb)

bugs [bug history graph]

all: 4
RC: 1
I&N: 3
M&W: 0
F&P: 0
patch: 0

links

homepage
buildd: logs, exp, reproducibility
popcon
browse source code
other distros
security tracker
screenshots
l10n (-, 83)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3:5.2.16-1