| Summary: | Request to update/rebase from 0.10.5 to 12.2 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Rob Marti <robmartiwork> |
| Component: | trac | Assignee: | David Cantrell <dcantrell> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | el5 | CC: | dcantrell, opensource |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-19 17:04:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Rob Marti
2011-04-04 18:49:04 UTC
I would like to use trac 0.12 from EPEL 5. How can we move this forward? Doing so would mean packaging it parallel installable with existing trac. The upgrade will leave sites broken until an admin takes manual action. Not only that, but many of the plugins will need work, some may have to use python26 builds as they require new python to work with track 0.12. This is not a small undertaking, and one I'm not willing to do. Interested parties should try creating a trac012 package for inclusion. |