|
Number of commits found: 5
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
1.2.2
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  ) |
1.2.2
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. |
1.2.2
23 Apr 2020 15:18:10
|
kai |
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. |
1.2.2
09 Apr 2020 07:36:36
|
kai |
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 .
Changelog:
https://github.com/matthiask/django-js-asset/blob/1.2.2/CHANGELOG.rst |
1.1.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: 5
|
As an Amazon Associate I earn from qualifying purchases.
