Bug 1647611
| Summary: | EPEL7 - python-django won't install on RHEL 7.6 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Troy Dawson <tdawson> |
| Component: | python-django16 | Assignee: | Stephen Gallagher <sgallagh> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | bkabrda, jakub.dornak, jal233, lonordtea, mhroncok, michel, mrunge, sgallagh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-django16-1.6.11.7-5.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-12-19 00:39:23 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: | |||
| Bug Blocks: | 1647564 | ||
|
Description
Troy Dawson
2018-11-07 22:11:05 UTC
There is a new package python-django16 that contains the packages python2-django python-django-bash-completion As you can see, the subpackage python-django-bash-completion conflicts between the two packages. I am not the package maintainer, but if it were me, I'd either remove the python-django package, or update the new python-django16 so that the bash-completion is python2-django-bash-completion Why has python-django16 been added to EPEL7 when python-django is 1.6 @EPEL7 as well? (In reply to Miro Hrončok from comment #2) > Why has python-django16 been added to EPEL7 when python-django is 1.6 @EPEL7 > as well? The python-django maintainer (Matthias Runge) asked me to split off 1.6 into its own package because he had planned to upgrade EPEL 7 to be a more modern Django installation. I still need this ancient version because it's used by Review Board. Apparently Matthias never followed through on the upgrade. Someone should take over the ownership of python-django and upgrade it or retire it. My python-django16 package does have a bug in it though (it should be building python-django16-bash-completion). I just pushed a fix and it's building now. python-django16-1.6.11.7-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-bac5bfddaf (In reply to Stephen Gallagher from comment #3) > (In reply to Miro Hrončok from comment #2) > > Why has python-django16 been added to EPEL7 when python-django is 1.6 @EPEL7 > > as well? > > The python-django maintainer (Matthias Runge) asked me to split off 1.6 into > its own package because he had planned to upgrade EPEL 7 to be a more modern > Django installation. I still need this ancient version because it's used by > Review Board. Apparently Matthias never followed through on the upgrade. > Someone should take over the ownership of python-django and upgrade it or > retire it. Ugh, I'm sorry about this. For me, it turned out, that EPEL has some severe issues itself, and I currently don't have an interest in maintaining anything in EPEL. iirc, we should have an antique version of Django in EPEL. Upgrading to a more modern (and still supported) version would be the upgrade to 1.11. I've filed https://pagure.io/epel/issue/48 (In reply to Stephen Gallagher from comment #3) > (In reply to Miro Hrončok from comment #2) > > Why has python-django16 been added to EPEL7 when python-django is 1.6 @EPEL7 > > as well? > > The python-django maintainer (Matthias Runge) asked me to split off 1.6 into > its own package because he had planned to upgrade EPEL 7 to be a more modern > Django installation. I still need this ancient version because it's used by > Review Board. Apparently Matthias never followed through on the upgrade. > Someone should take over the ownership of python-django and upgrade it or > retire it. Thanks for clarification. > My python-django16 package does have a bug in it though (it should be > building python-django16-bash-completion). I just pushed a fix and it's > building now. And thanks for the fix! python-django16-1.6.11.7-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-bac5bfddaf python-django-1.11.13-4.el7, python-django16-1.6.11.7-5.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2206653eb9 The fixed package has reached it's testing time. Does anyone mind if I push it to stable? Thanks for the heads-up. I just pushed both python-django packages to batched. Since this is an upgrade, we wanted some feedback, which did not really happen. python-django-1.11.13-4.el7, python-django16-1.6.11.7-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. graphite-web-0.9.16-2.el7 is currently broken as it requires `python-django >= 1.3` and the new package has meant it’s leapt from 1.6 -> 1.11 which is incompatible. The spec file requires needs toT be updated to require "python2-django16 >= 1.3" (In reply to lonordtea from comment #12) > graphite-web-0.9.16-2.el7 is currently broken as it requires `python-django > >= 1.3` and the new package has meant it’s leapt from 1.6 -> 1.11 which is > incompatible. > > The spec file requires needs toT be updated to require "python2-django16 >= > 1.3" That bug needs to be filed against graphite-web. |