| Port details |
- py-dj22-django-timezone-field Provides database and form fields for pytz timezone objects for Django
- 4.0 www
 =0      4.0Version of this port present on the latest quarterly branch.  DEPRECATED: Obsolete, please use www/py-django-timezone-field instead
 This port expired on: 2020-06-30
- Maintainer: kai@FreeBSD.org
- Port Added: 2019-05-25 10:11:19
- Last Update: 2020-06-30 10:32:54
- SVN Revision: 540890
- Also Listed In: python
- License: BSD2CLAUSE
- WWW:
- https://github.com/mfogel/django-timezone-field
- Description:
- Provides database and form fields for pytz timezone objects for Django.
WWW: https://github.com/mfogel/django-timezone-field
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}dj22-django-timezone-field>0:www/py-dj22-django-timezone-field@${PY_FLAVOR}
- Conflicts:
- CONFLICTS_INSTALL:
- py37-django-timezone-field
- No installation instructions:
- This port has been deleted.
- PKGNAME: py37-dj22-django-timezone-field
- Package flavors (<flavor>: <package>)
- py37: py37-dj22-django-timezone-field
- distinfo:
- TIMESTAMP = 1576100374
SHA256 (django-timezone-field-4.0.tar.gz) = 7e3620fe2211c2d372fad54db8f86ff884098d018d56fda4dca5e64929e05ffc
SIZE (django-timezone-field-4.0.tar.gz) = 6866
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- Runtime dependencies:
-
- py37-django22>=2.2 : www/py-django22@py37
- py37-pytz>0 : devel/py-pytz@py37
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- USES:
- python:3.5+
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 6
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
4.0
30 Jun 2020 10:32:54
  |
rene |
Remove expired ports:
2020-06-30 databases/p5-Search-Xapian10: Depend on unsupported xapian-core. Use
databases/p5-Search-Xapian instead
2020-06-30 databases/xapian-core10: Unsupported by upstream. Use
databases/xapian-core instead
2020-06-30 devel/py-dj22-django-rq: Obsolete, please use www/py-django-rq
instead
2020-06-30 devel/rubygem-cucumber-expressions: Use
devel/rubygem-cucumber-cucumber-expressions instead
2020-06-30 devel/rubygem-cucumber-expressions6: Use
devel/rubygem-cucumber-cucumber-expressions instead
2020-06-30 devel/rubygem-cucumber-tag_expressions1: Use
devel/rubygem-cucumber-tag_expressions instead
2020-06-30 print/xpp: Last update as 2004-12-09, unsupported by upstream
2020-06-30 textproc/rubygem-gherkin: Use textproc/rubygem-cucumber-gherkin
instead
2020-06-30 www/p5-Catalyst-Model-Xapian10: Depend on unsupported xapian-core.
Use www/p5-Catalyst-Model-Xapian instead
2020-06-30 www/py-dj22-django-auth-ldap: Obsolete, please use
www/py-django-auth-ldap instead
2020-06-30 www/py-dj22-django-cacheops: Obsolete, please use
www/py-django-cacheops instead
2020-06-30 www/py-dj22-django-cors-headers: Obsolete, please use
www/py-django-cors-headers instead
2020-06-30 www/py-dj22-django-crispy-forms: Obsolete, please use
www/py-django-crispy-forms instead (Only the first 15 lines of the commit message are shown above  ) |
4.0
24 Jun 2020 21:13:09
|
kai |
Set a few repo-copied py-dj22- ports to expire
* These ports were already set as DEPRECATED some time ago and now have no
consumers left as those have been switched back to the original ports. |
4.0
06 Apr 2020 07:52:06
|
kai |
www/py-django-timezone-field: Update to 4.0
* Also assign it to Django 2.2 (current LTS release) as Django 1.11 is
End-of-Life since April 2020.
* Set the repo-copied port www/py-dj22-django-timezone-field as DEPRECATED
because it's obsolete now. Don't set an expiration date yet as it's still
used by net-mgmt/netbox and a few more Django 1.11 ports need to be
assigned to Django 2.2 first.
* Also update the CONFLICTS_INSTALL entries as the repo-copied port
py-dj21-django-timezone-field no longer exists in the Ports tree.
Changelog:
* Add support for Django 3.0 and Python 3.8
* Drop support for Django 1.11, 2.0, 2.1 and Python 2.7, 3.4
PR: 245309 |
4.0
13 Dec 2019 11:41:16
|
kai |
www/py-dj22-django-timezone-field: Update to 4.0
Changelog:
* Add support for Django 3.0 and Python 3.8
* Drop support for Django 1.11, 2.0, 2.1 and Python 2.7, 3.4 |
3.1
03 Nov 2019 11:54:39
|
kai |
www/py-{dj21,dj22}-django-timezone-field: Update to 3.1
Changelog:
* Officially support django 2.2 (already worked)
* Add option to display TZ offsets in form field |
3.0
25 May 2019 10:10:01
|
kai |
net-mgmt/netbox: Update to 2.5.12 and switch to Django 2.2
Upstream decided to switch from Django 2.1 to the 2.2 LTS release to fix a
rather annoying bug that generated intermittent errors when objects were
deleted/manipulated.
Therefore the same procedure must be done in almost the same way as in
r492690 to make NetBox compatible with Django 2.2 in the ports tree.
That means to repocopy the required Django 1.11 ports, assign them to
Django 2.2, limit them to Python 3.5+ and update all related
CONFLICTS_INSTALL entries accordingly:
* www/py-dj22-django-cors-headers [1]
* www/py-dj22-django-debug-toolbar (Only the first 15 lines of the commit message are shown above ) |
Number of commits found: 6
|
As an Amazon Associate I earn from qualifying purchases.