notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
NOTE: the WWW: line in pkg-descr was relocated to a WWW= line in Makefile. Each port in FreshPorts has a homepage link. Look for it right after the Description: on each port's home page.

Do I know someone who can pick up a server from 7401 E. Ben White Blvd. Austin TX?

The emphasis is on know, or recommended by someone I know. This is the original FreshPorts server, way past useful: RAID, 8GB RAM, etc. The drives need to be wiped and everything recycled.
Port details
py-dj22-django-js-asset Insert script tags with additional attributes for django.forms.Media
1.2.2 www Deleted on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout Version of this port present on the latest quarterly branch.
Deprecated DEPRECATED: Obsolete, please use www/py-django-js-asset instead
Expired This port expired on: 2020-06-30
Maintainer: search for ports maintained by this maintainer
Port Added: 2019-05-25 10:11:19
Last Update: 2020-06-30 10:32:54
SVN Revision: 540890
Also Listed In: python
pkg-plist: as obtained via: make generate-plist
There is no configure plist information for this port.
Dependency lines:
  • ${PYTHON_PKGNAMEPREFIX}dj22-django-js-asset>0:www/py-dj22-django-js-asset@${PY_FLAVOR}
  • py37-django-js-asset
Conflicts Matches:
There are no Conflicts Matches for this port. This is usually an error.
No installation instructions:
This port has been deleted.
PKGNAME: py37-dj22-django-js-asset
Package flavors (<flavor>: <package>)
  • py37: py37-dj22-django-js-asset

No package information for this port in our database
Sometimes this happens. Not all ports have packages.

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. py37-setuptools>0 : devel/py-setuptools@py37
  2. python3.7 : lang/python37
Runtime dependencies:
  1. py37-django22>0 : www/py-django22@py37
  2. py37-setuptools>0 : devel/py-setuptools@py37
  3. python3.7 : lang/python37
NOTE: dependencies for deleted ports are notoriously suspect
This port is required by:
for Run

Deleted ports which required this port:

Expand this list of 1 deleted port
  1. www/py-dj22-django-mptt*
  2. Collapse this list of deleted ports.
* - deleted ports are only shown under the This port is required by section. It was harder to do for the Required section. Perhaps later...

Configuration Options:
Options name:


FreshPorts was unable to extract/find any pkg message
Master Sites:
Expand this list (2 items)
Collapse this list.
Collapse this list.
Port Moves
  • port moved to www/py-django-js-asset on 2020-06-30
    REASON: Has expired: Obsolete, please use www/py-django-js-asset instead
  • port moved here from www/py-dj21-django-js-asset on 2020-01-31
    REASON: Has expired: 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

Number of commits found: 5

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
30 Jun 2020 10:32:54
Revision:540890Original commit files touched by this commit
rene search for other commits by this committer
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
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
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 View all of this commit message)
24 Jun 2020 21:13:09
Revision:540349Original commit files touched by this commit
kai search for other commits by this committer
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.
23 Apr 2020 15:18:10
Revision:532684Original commit files touched by this commit
kai search for other commits by this committer
www/py-dj22-django-{mptt,js-asset}: Deprecate

* Set both ports as DEPRECATED after r532664 and r532683 because they're
  obsolete now.

  Don't set an expiration date yet as both ports are still used by
  net-mgmt/netbox and a few more ports still need to be switched from
  Django 1.11 to Django 2.2.
09 Apr 2020 07:36:36
Revision:531189Original commit files touched by this commit
kai search for other commits by this committer
www/py-dj22-django-js-asset: Update to 1.2.2

* Update CONFLICTS_INSTALL as www/py-dj21-django-js-asset no longer exists
  in the Ports tree.

* Sync with www/py-django-js-asset from r531188 .

25 May 2019 10:10:01
Revision:502550Original commit files touched by this commit
kai search for other commits by this committer
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

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 View all of this commit message)

Number of commits found: 5