ports that depend on expired Django 1.6
René Ladan
rene at freebsd.org
Sat Feb 25 22:35:44 UTC 2017
Hi,
Django 1.6 expired in the Ports Tree almost 17 months ago, on 2015-10-01
(see [1]). I intend to clean it up together with django-pipeline13,
which is also overdue, on 2017-04-01.
This leaves the following ports broken:
* www/py-djblets (see PR 216758): this is a leaf port originally meant
for www/reviewboard, which was removed again.
* www/py-cactus: this is a leaf port. There is a newer version 3.3.3
(see [2]) upstream but they still use Django 1.6.
security/py-crits: there is a pull request #818 (see [3]) to add support
for Django 1.8 and higher. This would enable removing
devel/py-django16-tastypie-mongoengine and www/py-django16-tastypie too.
[1] https://www.freshports.org/ports-expired.php?sort=expiration_date
[2] https://pypi.python.org/pypi/Cactus
[3]
https://github.com/crits/crits/pull/818/commits/eeae60aece32d740807889cc5f2feef073771e06
What do you think?
Regards,
René
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-python/attachments/20170225/ad2a3bca/attachment.sig>
More information about the freebsd-python
mailing list