Bug 263771
| Summary: | www/py-django-modern-rpc: Deprecate/Set to expire or switch to 1.0 Alpha release | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Kai Knoblich <kai> | ||||
| Component: | Individual Port(s) | Assignee: | Kai Knoblich <kai> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | sunpoet | ||||
| Priority: | --- | Flags: | sunpoet:
maintainer-feedback+
|
||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| URL: | https://github.com/alorence/django-modern-rpc/releases/tag/1.0.0a1 | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 261313 | ||||||
| Attachments: |
|
||||||
I'm OK to deprecate this port. Thanks! Comment on attachment 233716 [details] deprecate-py-django-modern-rpc.patch ^Triage: Setting maintainer-approval flag to '+' as it was given via comment #1. A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=a15f89636414e85acb8a803beac4829d237a011d commit a15f89636414e85acb8a803beac4829d237a011d Author: Kai Knoblich <kai@FreeBSD.org> AuthorDate: 2022-05-14 04:45:18 +0000 Commit: Kai Knoblich <kai@FreeBSD.org> CommitDate: 2022-05-14 04:45:18 +0000 www/py-django-modern-rpc: Deprecate/Set to expire * Django 2.2 is End-of-Life since April 2022 and the current release of this port isn't compatible with newer versions of Django. PR: 263771 Approved by: sunpoet (maintainer) www/py-django-modern-rpc/Makefile | 3 +++ 1 file changed, 3 insertions(+) (In reply to Po-Chuan Hsieh from comment #1) Committed, thanks! |
Created attachment 233716 [details] deprecate-py-django-modern-rpc.patch Hi Sunpoet, attached is a patch that would deprecate www/py-django-modern-rpc and set an expiration date to it as the current version of the port doesn't seem to work with Django 3.2. There's also 1.0.0 Alpha available at the upstream repository, which contain support for Django 3.2, that might be used. Another option would be, if the 0.12.1 release (not available at PyPI) of www/py-django-modern-rpc still works with Django 3.2, to switch the port over to Django 3.2. Which of these options would you prefer?