Bug 493073

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

We're planning to move the opensync.org and talking about choice of platform as there are multiple people with different distro experience.

I'd prefer the platform that can utilize epel packages, but trac version became an issue. We have already migrated in current environment to 0.11 and moving backwards is not an option as those added features are needed.

So, opinions about upgrading the epel* versions to 0.11? Just work or is there any blockers?

The problem with upgrading to 0.11 is that it is a db format change that will require admin interaction (cannot be scripted) or else existing project spaces will stop working.  This is not something usually done within a stable release (EL5).  There was some effort put into making a parallel installable package of trac0.11 but that was going to be loads of pain with all the plugins we use.  I have considered packaging 0.11 up for EL5 to put in the infrastructure repo and use that version but I think we ran into some python version compatibility issues.  I'll look into it again shortly.

(In reply to comment #3)
> The problem with upgrading to 0.11 is that it is a db format change that will
> require admin interaction (cannot be scripted) or else existing project spaces
> will stop working.  This is not something usually done within a stable release
> (EL5).  There was some effort put into making a parallel installable package of
> trac0.11 but that was going to be loads of pain with all the plugins we use.  I
> have considered packaging 0.11 up for EL5 to put in the infrastructure repo and
> use that version but I think we ran into some python version compatibility
> issues.  I'll look into it again shortly.  

Jesse,

I have been using trac-0.11.x in CentOS 5.x for almost a year quite happily (with python 2.4.x).

The only problem I faced was with the sqlite support: a trac plugin forced me
to bump the requirement to python-sqlite2 as the python-sqlite interface was non DB-API 2.0 compliant.

/jpo

PS - trac 0.11.5 RC 1 is already available
     http://trac.edgewall.org/wiki/TracDownload#LatestReleaseCandidate
     http://trac.edgewall.org/milestone/0.11.5

Jpo, are you suggesting that it could be upgraded to EL5?

The problem with Trac-0.11 in EL5 is also that plugins will not work.  Some of the plugins we use, particularly the trac-git-plugin, require python 2.5+ for the 0.11 version of the plugins.  Thus we'd be left without those plugins if we put Trac-0.11 in EL5, as EL5 has python-2.4.

So no, we won't be updating Trac to 0.11 in EL5, nor in Fedora Hosted.  Once EL6 is released we will migrate Fedora Hosted to it and trac 0.11 (or 12 if it's out by then)

trac-0.11.4-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/trac-0.11.4-1.fc11

trac-0.11.4-1.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update trac'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7883

trac-0.11.4-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.