Description of problem: The latest upstream version of branch 0.12 is 0.12.5. Version-Release number of selected component (if applicable): trac-0.12.4-1.el6 Expected results: To have trac version 0.12.5 available in EPEL6. Additional info: Trivial update Download: http://trac.edgewall.org/wiki/TracDownload http://download.edgewall.org/trac/Trac-0.12.5.tar.gz Closed tickets: http://trac.edgewall.org/milestone/0.12.5 http://trac.edgewall.org/query?status=closed&group=resolution&milestone=0.12.5 http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.12#MaintenanceReleases Changelog: http://trac.edgewall.org/browser/tags/trac-0.12.5/ChangeLog
Created attachment 692498 [details] Trac specfile patch: update from 0.12.4 to 0.12.5 The attached patch updates the EPEL6 specfile from version 0.12.4 to version 0.12.5. /jpo
Trac 1.0 is now considered current by Trac. Any reason not to move up to the latest?
I'll update the version to 0.12.6. As far as I'm concerned we can't update to 1.0 because that would be a breaking change and unfortunately EPEL does not have a mechanism for having breaking changes (e.g. with some kind of bi-yearly "update X+1" releases).
actually Trac 0.12.5 is already available from EPEL6 for quite a while so we can close this bug. I'll push an update to 0.12.6 nevertheless.
Any chance of a separate set of packages for, say, trac10?
Or at least Trac 1.x for RHEL 7?
I think the basic problem is that Trac gets upstream support for maybe 3-4 years but ideally we should maintain EPEL packages until the corresponding RHEL version is end-of-life. If we had a mechanism to introduce breaking changes for EPEL in a defined manner (similar to RHEL's update versions) we could easily ship the latest stable Trac version. The best thing next to that might be a copr repo for EPEL shipping the latest stable Trac version (parallel installable). If you're interested in that (and able to put some effort) best contact me directly.