| Port Moves |
- port deleted on 2026-08-31
REASON: Has expired: Serves as a transition only for www/seahub and requires Django 4.2, which has been end-of-life since April
|
Number of commits found: 3
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
0.2.0 31 Aug 2026 10:45:21
    |
Rene Ladan (rene)  |
www/py-dj42-django-ranged-response: Remove expired port
2026-08-31 www/py-dj42-django-ranged-response: Serves as a transition only for
www/seahub and requires Django 4.2, which has been end-of-life since April |
0.2.0 27 May 2026 20:02:14
    |
Richard Gallamore (ultima)  |
*: Drop maintainership |
0.2.0 26 May 2026 11:24:35
    |
Kai Knoblich (kai)  |
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 (Only the first 15 lines of the commit message are shown above ) |
Number of commits found: 3
|