[Bug 291707] [META] Deprecate/Expire Django 4.2 and switch to Django 5.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291707

Kai Knoblich <kai@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siva@FreeBSD.org,
                   |                            |ultima@freebsd.org
           See Also|                            |https://reviews.freebsd.org
                   |                            |/D56966
             Status|New                         |In Progress

--- Comment #7 from Kai Knoblich <kai@FreeBSD.org> ---
(In reply to Po-Chuan Hsieh from comment #6)

Thanks, but we're not quite there yet. There are still a few showstoppers at
the moment:

Trivial ones:
~~~~~~~~~~~~~

There is no newer release available at this time of writing for any of the
following three ports, so a few adjustments are necessary.

- mail/py-django-mailman3 -> Needs an expanded range for Django 5.2 (adjust
Makefile and pyproject.toml)
- www/py-postorius -> ditto (adjust Makefile and pyproject.toml)
- www/py-hyperkitty -> ditto (adjust pyproject.toml)

These adjustments can also be applied directly during the migration to Django
5.2.


Not so trivial ones:
~~~~~~~~~~~~~~~~~~~~
- devel/py-sortinghat:

siva@ is already working on it, and the actual plan is to update py-sortinghat
et al. before the entire ports are migrated to Django 5.2.

After that, py-sortinghat would depend on some py-dj52* ports for a short while
and would be decoupled from the entire Django 5.2 migration.


- www/seahub:

ultima@ is working on this, and the task isn't exactly trivial given the
complexity of net-mgmt/seafile-* ports.

I assume that updating www/seahub and net-mgmt/seafile-* immediately afterwards
as a separate commit following the migration of the ports to Django 5.2 seems
the best approach so far.


I also created review D56966 for the Django 5.2 migration. Once we've figured
out the best way to handle devel/py-sortinghat and www/seahub, I'll add the
reviewers.

-- 
You are receiving this mail because:
You are the assignee for the bug.