[Bug 261086] www/py-graphite-web: conflicts with net-mgmt/netbox: django22 versus django32
Date: Sun, 13 Feb 2022 10:38:44 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261086
Kai Knoblich <kai@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |261313
See Also| |https://github.com/graphite
| |-project/graphite-web/issue
| |s/2703,
| |https://github.com/graphite
| |-project/graphite-web/issue
| |s/2732
--- Comment #2 from Kai Knoblich <kai@FreeBSD.org> ---
Switching www/py-graphite-web to Django 3.2, once upstream supports it, would
indeed fix the reported issue.
But the problem will come back with NetBox 3.2, which will be released in
April, and requires then Django 4.0 to run.
It's a known issue with Django as one version cannot co-exist with other
versions of Django. Some effort was made some time ago to simplify the use of
different Django versions, see review D12592. But it still requires some work
to get it into the Ports tree.
A workaround to cope with the different Django versions would be to use
isolated instances via jails.
Regarding www/py-graphite-web and Django 3.2:
The current release (= 1.1.8) doesn't support Django 3.x (see issue #2703) and
there's a new release planned (see issue #2732). However, it's currently not
possible to say whether the new release will also support Django 3.x.
I also connect this bug with bug #261313 because it's related to the switchover
from Django 2.2 (= EoL in April 2022) to Django 3.2 (= next LTS release).
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261313
[Bug 261313] [META] Deprecate/Expire Django 2.2 and switch to Django 3.2
--
You are receiving this mail because:
You are the assignee for the bug.