Bug 2190360
Summary: | Requesting EPEL9 build of django | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Steve Traylen <steve.traylen> |
Component: | python-django | Assignee: | Michel Lind <michel> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel9 | CC: | aekoroglu, mhroncok, michel, mrunge, rdopiera, sgallagh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-12 10:52:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2109163, 2133557, 2133559, 2133560, 2133561, 2210723 | ||
Bug Blocks: |
Description
Steve Traylen
2023-04-28 06:14:53 UTC
Heads up, this package is riddled with CVEs in EPEL: https://bugzilla.redhat.com/buglist.cgi?component=python-django&product=Fedora%20EPEL&status=__open__ For info building the 4.2 package is possible with the following stack built first. * python-asgiref * python-psycopg3 * python3-mypy * python-mypy_extensions * python-aiosmtpd * python-pymemcache * python-pylibmc * python-flufl-testing * python-cx-oracle * python-tblib Removing the python-black requirement drops a huge number of deps and have submitted same change for fedora. Can't remember where the mypy stuff came from but is also a linter of sorts to remove. A couple of tests fail: * test_readonly_root * test_permissions_error however they do also fail with a vanilla checkout of django-4.2.1 and a venv as well. Not to bad - putting this off till 3.11 starts to arrive may well make sense. (In reply to Steve Traylen from comment #2) > For info building the 4.2 package is possible with the following stack built > first. > * python-asgiref > * python-psycopg3 > * python3-mypy > * python-mypy_extensions > * python-aiosmtpd > * python-pymemcache > * python-pylibmc > * python-flufl-testing > * python-cx-oracle > * python-tblib > > Removing the python-black requirement drops a huge number of deps and have > submitted same change for fedora. Can't remember > where the mypy stuff came from but is also a linter of sorts to remove. > > A couple of tests fail: > > * test_readonly_root > * test_permissions_error > > however they do also fail with a vanilla checkout of django-4.2.1 and a venv > as well. > > Not to bad - putting this off till 3.11 starts to arrive may well make sense. Steve, some of us are interested in getting Django in and others so we can upgrade our mailing list infra. Are you interested in helping us out? We plan to fork Fedora's python-django to python-django4.2 to explicitly track the 4.2 LTS series (similar to how there's currently python-django3). I'm not interested. From my point of view I should close this. |