Description of problem: Trac 0.10 is no longer maintained.[1] Consider updating to Trac 0.12, which does build on EL5 and EL6.[2] Version-Release number of selected component (if applicable): trac-0.10.x-x How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: N/A Expected results: N/A Additional info: [1] per Trac Download Page: http://trac.edgewall.org/wiki/TracDownload#LatestStableReleaseforthe0.10.xline-0.10.5 [2] RPMForge (rf) builds Trac 0.12 for both EL5 and EL6: http://packages.sw.be/trac/ There is only one, additional dependency issue. Package python-genshi 0.6 is required. Version 0.5 is in EPEL for EL5: http://koji.fedoraproject.org/koji/packageinfo?packageID=4513 And Red Hat EL6 ships python-genshi 0.5 as well. But the current EPEL strategy for EL6 is providing a python-genshi06 package ("06" appended) to address this: http://koji.fedoraproject.org/koji/packageinfo?packageID=11244 So it should be easy to adopt this same strategy on EPEL for EL5. Please consider addressing this long-term in Fedora/EPEL with a single, multi-dist SPEC/SRPMS for F15+, EL5 and EL6 with python-genshi[06]-0.6 ("06" not appended for F15+) and trac-0.12 package release. The conditionals required should be minimal. Another note: Red Hat EL 5.6 Beta rebases Subversion from 1.4 to 1.6. Doing the same with Trac for the EL 5.6 release would be ideal timing.
The problem here is that upgrading trac from 0.10 to anything newer will break existing project databases, unitl an admin manually "upgrades" the database. Since trac DBs can exist in any number of places, it would be impossible (and irresponsible) to attempt to automatically upgrade them from within rpm. Add to that there are a number of important plugins which require a newer python in order to work with newer trac versions. This would leave a lot of functionality in the lurch, or require a massive undertaking of bringing a new python to EL5. In short, we are not going to update Trac in EL5. As security issues are found we will do our best to backport them to the 0.10 code set.
Understand the first point, and done it myself. Although seeing one-off Trac versions in different Fedora and EPEL releases is interesting. At some point it might be nice to unify them. The second point, I was not aware of. Is it possible, without much overhead, to built a "trac012" package? That way: 1. It is more unified in Fedora and EPEL 2. It doesn't break existing Trac 0.10 or 0.11 databases on older Fedora/EL releases 3. It doesn't break existing plug-ins on older Fedora/EL releases 4. Those with newer plug-in requirements will just migrate to newer distros Just a suggestion.
Another consideration for the second point ... Build Trac 0.12 against Python 2.6, as the concurrent "python26" packages are now being included in EPEL now to deal with other Python dependency considerations in various other packages. This also matches the Python in RHEL6, and would address the Trac plug-in dependency issues. A newer Python also opens doors on using things other than mod_python as well. I know there are many comments and views out there about using mod_python. Not trying to stomp on the charity and efforts of others in the Fedora Project working on EPEL by telling anyone what to do. Just trying to find a way forward to get off these older Trac versions, especially 0.10 which isn't supported. In some cases, these may actually reduce headaches.
You're more than welcome to investigate a trac012 package for EPEL, built against python26 and potentially python-genshi06. But that would be a review request bug, not an RFE bug. As for upgrading the existing one, we're not going to do it. We won't stop anybody from working on the review though.
*** Bug 658954 has been marked as a duplicate of this bug. ***