|Summary:||CREATE DEFAULT_VERSIONS for DJANGO|
|Product:||Ports & Packages||Reporter:||dgilbert|
|Component:||Ports Framework||Assignee:||freebsd-python mailing list <python>|
|Severity:||Affects Only Me||CC:||matthew, ports-bugs|
Description dgilbert 2017-10-01 20:04:25 UTC
Even in my own work ... with a small number of projects, I'm supporting a number of different django versions. This works acceptably well in different jails to contain the software strangeness, but I've recently had to build ports by hand that depend on django to source the correct major version. ... anyways... I mentioned this in PR 219713 and koobs@FreeBSD.org also said that's what was needed.
Comment 1 Mathieu Arnold 2017-10-04 12:31:29 UTC
over to www/py-django's maintainer.
Comment 2 Matthew Seaman 2017-10-04 12:47:49 UTC
I have some work-in-progress that implements this. I'll post a review this evening.
Comment 3 Matthew Seaman 2017-10-05 08:48:44 UTC
Review posted at https://reviews.freebsd.org/D12592
Comment 4 Matthew Seaman 2017-10-08 17:24:18 UTC
Can we try an exp run with the latest diff from D12592?
Comment 5 dgilbert 2020-03-30 16:02:52 UTC
This is becoming more urgent. django-11 is marked as vulnerable and yet it is the only version for dependant ports. We might as well not have any django dependant ports if this is the case.