Created attachment 249453 [details] deprecate-py-django-ldapdb.patch Hi, the www/py-django-ldapdb port you maintain isn't compatible with Django 4.2 or later. See also issue #207 at the upstream repository for more details. The issue there has been reported two years ago and there's no permanent fix so far. Because Django 3.2 reaches its EoL (= End-of-Life) in April the port should be deprecated with an expiration date. > [...] > File "/usr/local/lib/python3.9/site-packages/ldapdb/models/__init__.py", line 5, in <module> > from ldapdb.models.base import Model # noqa > File "/usr/local/lib/python3.9/site-packages/ldapdb/models/base.py", line 12, in <module> > from . import fields as ldapdb_fields > File "/usr/local/lib/python3.9/site-packages/ldapdb/models/fields.py", line 367, in <module> > EPOCH = timezone.utc.localize(datetime.datetime.utcfromtimestamp(0)) > AttributeError: 'datetime.timezone' object has no attribute 'localize'
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=45210ce5f4b39210567916e69025df576051d578 commit 45210ce5f4b39210567916e69025df576051d578 Author: Kai Knoblich <kai@FreeBSD.org> AuthorDate: 2024-04-24 04:00:47 +0000 Commit: Kai Knoblich <kai@FreeBSD.org> CommitDate: 2024-04-24 04:03:01 +0000 www/py-django-ldapdb: Deprecate/Set to expire * The code is not compatible with Django 4.2 or newer and upstream no longer seems to be maintained. Thus deprecate the port and set an expiration date. PR: 277928 Approved by: maintainer timeout (3+ weeks) www/py-django-ldapdb/Makefile | 3 +++ 1 file changed, 3 insertions(+)
Comment on attachment 249453 [details] deprecate-py-django-ldapdb.patch ^Triage: Setting maintainer-approval flag to '+' due maintainer's timeout.