| Port details |
- py-dj22-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: Obsolete, please use www/py-django-taggit-serializer 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: 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}dj22-django-taggit-serializer>0:www/py-dj22-django-taggit-serializer@${PY_FLAVOR}
- Conflicts:
- CONFLICTS_INSTALL:
- py37-django-taggit-serializer
- py37-dj21-django-taggit-serializer
- No installation instructions:
- This port has been deleted.
- PKGNAME: py37-dj22-django-taggit-serializer
- Package flavors (<flavor>: <package>)
- py37: py37-dj22-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:
-
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- Runtime dependencies:
-
- py37-dj22-django-taggit>=0 : www/py-dj22-django-taggit@py37
- py37-six>=0 : devel/py-six@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: 4
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.1.7
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  ) |
0.1.7
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. |
0.1.7
29 May 2020 15:10:38
|
kai |
www/py-dj22-django-taggit-serializer: Deprecate
* The port became obsolete after www/py-django-taggit was switched to
Django 2.2 in r534835. Don't set an expiration date yet as the port is
still used by net-mgmt/netbox. |
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 ) |
Number of commits found: 4
|
As an Amazon Associate I earn from qualifying purchases.