Date: Fri, 17 Apr 2020 03:48:23 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 245365] www/py-django-jsonfield : Update to 3.1.0 Message-ID: <bug-245365-21822-FURhYw5nuw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245365-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-245365-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245365 Richard Gallamore <ultima@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #6 from Richard Gallamore <ultima@freebsd.org> --- I'm in favor with sunpoet's solution of only one port being necessary. I do= n't see the point of having the py-django-jsonfield port any longer and with the merge and rename to py-jsonfield. Going to update the port to version 2.1.1 and set a deprecation message. On= ce Seafile has upgraded django I'll change the depends and remove the port pointing to py-jsonfield. This is mainly to prevent delays for updating to = v3. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245365-21822-FURhYw5nuw>