| Port details |
- py-dj21-django-taggit-serializer Django Taggit serializer for the Django REST Framework
- 0.1.7 www
 =0      0.1.7Version of this port present on the latest quarterly branch.  DEPRECATED: Django 2.1 is now End-of-Life (Since December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this port as soon as possible
 This port expired on: 2020-01-31
- Maintainer: kai@FreeBSD.org
- Port Added: 2019-02-11 12:03:08
- Last Update: 2020-01-31 13:54:08
- SVN Revision: 524704
- Also Listed In: python
- License: BSD3CLAUSE
- WWW:
- https://github.com/glemmaPaul/django-taggit-serializer
- Description:
- This package makes it possible to serialize tags generated by the django-taggit
package. Because the tags in the django-taggit package need to be added into a
TaggableManager() one cannot use the usual Serializer that is retrieved from the
Django REST Framework.
WWW: https://github.com/glemmaPaul/django-taggit-serializer
 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}dj21-django-taggit-serializer>0:www/py-dj21-django-taggit-serializer@${PY_FLAVOR}
- Conflicts:
- CONFLICTS_INSTALL:
- py36-django-taggit-serializer
- py36-dj22-django-taggit-serializer
- No installation instructions:
- This port has been deleted.
- PKGNAME: py36-dj21-django-taggit-serializer
- Package flavors (<flavor>: <package>)
- py36: py36-dj21-django-taggit-serializer
- distinfo:
- TIMESTAMP = 1533884090
SHA256 (django-taggit-serializer-0.1.7.tar.gz) = f712eb2482079be452bcd1e82b18a820e26427c3ee1cef2b4fcd4d6b8b9f14d0
SIZE (django-taggit-serializer-0.1.7.tar.gz) = 5589
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:
-
- py36-setuptools>0 : devel/py-setuptools@py36
- python3.6 : lang/python36
- Runtime dependencies:
-
- py36-dj21-django-taggit>=0 : www/py-dj21-django-taggit@py36
- py36-six>=0 : devel/py-six@py36
- py36-setuptools>0 : devel/py-setuptools@py36
- python3.6 : lang/python36
- 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: 4
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.1.7
31 Jan 2020 13:54:08
  |
rene |
Remove expired ports:
2020-01-31 www/py-dj21-django-auth-ldap: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 www/py-dj21-django-crispy-forms: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 www/sogo3-activesync: Deprecated, replaced by www/sogo4
2020-01-31 devel/sope3: Deprecated, replaced by devel/sope4
2020-01-31 www/py-dj21-django-mptt: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 graphics/py-willow11: Use graphics/py-willow instead
2020-01-31 www/py-dj21-django-tables2: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 www/py-dj21-django-debug-toolbar: Django 2.1 is now End-of-Life
(Since December 2 2019) and no longer supported. Switch to Django 2.2+ versions
of this port as soon as possible
2020-01-31 security/krb5-115: EOL one year after the release of krb5 1.17
2020-01-31 www/py-dj21-django-taggit: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 www/py-dj21-django-cors-headers: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 graphics/py-imgurpython: No longer supported by upstream
2020-01-31 www/py-dj21-django-taggit-serializer: Django 2.1 is now End-of-Life
(Since December 2 2019) and no longer supported. Switch to Django 2.2+ versions
of this port as soon as possible
2020-01-31 www/py-dj21-django-filter: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 www/py-dj21-django-timezone-field: Django 2.1 is now End-of-Life
(Since December 2 2019) and no longer supported. Switch to Django 2.2+ versions
of this port as soon as possible
2020-01-31 devel/py-xarray011: Use devel/py-xarray instead
2020-01-31 www/py-django-modelcluster4: Use www/py-django-modelcluster instead
2020-01-31 devel/py-semantic_version26: Use devel/py-semantic_version instead
2020-01-31 www/py-dj21-django-js-asset: Django 2.1 is now End-of-Life (Since
December 2 2019) and no longer supported. Switch to Django 2.2+ versions of this
port as soon as possible
2020-01-31 www/py-dj21-drf-yasg: Django 2.1 is now End-of-Life (Since December 2
2019) and no longer supported. Switch to Django 2.2+ versions of this port as
soon as possible |
0.1.7
04 Dec 2019 12:02:32
|
kai |
www/py-django21 (and dj21 ports): Deprecate / set expiration date
Django 2.1 reached its End-of-Life (EoL) on 2nd December. Deprecate the port
and its consumers (= www/py-dj21-*) accordingly.
Set the expiration date to the end of January 2020 to give users enough time
to migrate to Django 2.2+ because the EoL is already onset and the
deprecation comes quite late.
Reviewed by: koobs (python: maintainer)
Approved by: koobs (python: maintainer)
Differential Revision: https://reviews.freebsd.org/D22668 |
0.1.7
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  ) |
0.1.7
11 Feb 2019 12:00:30
|
kai |
Create some ports that are assigned to Django 2.1 instead Django 1.11.
Django 1.11 is currently the "default" version in the ports tree due its
long term support until April 2020 thus ports that are assigned to that
version will exist until then.
The following packages are required to make the upgrade of net-mgmt/netbox
to 2.5.x possible because upstream has decided to switch from Django 1.11
to Django 2.1:
* www/py-dj21-django-cors-headers
* www/py-dj21-django-debug-toolbar
* www/py-dj21-django-filter
* www/py-dj21-django-js-asset
* www/py-dj21-django-mptt (Only the first 15 lines of the commit message are shown above ) |
Number of commits found: 4
|
As an Amazon Associate I earn from qualifying purchases.