Figure out our plan for when Django14 gets re-retired
Issue #1755 occurred because Django14 was removed from EPEL6. This caused such problems for users that the package is being temporarily brought back to EPEL6, but it's not a very good situation for 2 reasons.
1) The Django14 is known to be insecure and is not receiving updates from upstream Django or from the package maintainer in EPEL.
2) Django14 eventually will likely be re-retired at some point at which point if we take don't take proactive action we'll have #1755 again on our hands.
See the epel-devel thread on this issue where the future of Django14 is being discussed.
#2 Updated by bmbouter over 1 year ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue