*: Switch consumers over to Django 5.2 Django 4.2 reached its End-of-Life on 7th April 2026 and Django 5.2 is the new LTS (= Long Term Support) release which will be supported until April 2028. * Switch most ports that use www/py-django42 to www/py-django52. * Where necessary, remove PORTSCOUT, which is no longer needed because an update to a newer version that no longer supports Django 4.2 should now be possible. * Bump PORTREVISION due dependency change where necessary. PR: 291707 Reviewed by: sunpoet (python) Differential Revision: https://reviews.freebsd.org/D56966ce59801b72
Port details
www/py-djangosaml21.11.1_1
Pysaml2 integration for Django
- Maintainer
- ports@FreeBSD.org
- Packages
- py312-djangosaml2 1.11.1_1
- Upstream
- Higher version available: 1.12.0
- CPE
- none, CVEs only via VuXML
- WWW
- https://github.com/IdentityPython/djangosaml2
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (9)
*: Drop maintainershipec4fe6557e
net-mgmt/seafile-server,www/seahub: Deprecate Updating www/seahub, and especially net-mgmt/seafile-server, is more difficult than originally anticipated. The current version of www/seahub also only runs with Django 4.2, which has been end-of-life since April. Before www/seahub and net-mgmt/seafile-server are marked as BROKEN after the migration of the affected ports to Django 5.2 [1], and then vanish from the ports tree at the end of 2026Q2 - which would also break POLA due the short time period - do the following to buy some time for a possible update: * Create required py-dj42-* ports and switch www/seahub to them. These py-dj42-* ports were copied from their original counterparts, are bound to Django 4.2, and have also been adapted for the PEP517 build framework to make them future-proof. Also adjust related entries in MOVED. * Add CONFLICTS_INSTALL entries to the original counterparts as well where necessary. * Bump PORTREVISION of www/seahub due changed dependencies. * Set a suitable EXPIRATION_DATE to have enough time to work on an update. The EXPIRATION_DATE for www/py-django42 will adjusted accordingly afterwards. PR: 291707 [1] Reviewed by: ultima (maintainer) Differential Revision: https://reviews.freebsd.org/D5722774ee429290
www/py-djangosaml2: Update to 1.11.1 Changes: https://github.com/IdentityPython/djangosaml2/compare/v1.9.3..v1.11.1b283aa7d8f
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal Any missed ports, feel free to bump. Any ports that need setuptools at runtime can have the devel/py-setuptools manually added back to RUN_DEPENDS, but understand that this practice is deprecated; see CHANGES for details.06a08e69f3
www/py-djangosaml2: Updated to 1.9.3 Changes: https://github.com/IdentityPython/djangosaml2/releasesc561f3d36e
*: Switch consumers over to Django 4.2 Django 3.2 reached its End-of-Life on 1st April 2024 and Django 4.2 is the new LTS (= Long Term Support) release which will be supported until April 2026. * Switch most ports that use www/py-django32 to www/py-django42. * Ports that are not compatible with Django 3.2 have already been set with an expiration date were not taken into account. * Bump PORTREVISION due dependency change where necessary. PR: 276319 Reviewed by: dvl, grembo, ultima Approved by: bofh (implicit), dvl, grembo, Kevin Golding, sunpoet, ultima, maintainer timeout (remaining maintainers) Differential Revision: https://reviews.freebsd.org/D44637680c68fd4d
www/py-djangosaml2: Update to 1.9.2 Changes: https://github.com/IdentityPython/djangosaml2/releases990b7e71d5
www/py-djangosaml2: New port A Django application that builds a Fully Compliant SAML2 Service Provider on top of PySAML2 library. Djangosaml2 protects your project with a SAML2 SSO Authentication.d8312662f4