trac 0.11.3 has been released some time ago see http://trac.edgewall.org/wiki/TracDownload and http://trac.edgewall.org/browser/tags/trac-0.11.3/RELEASE Reproducible: Always Steps to Reproduce:
just renaming the ebuild to .3 works on amd64 for me, please bump in portage
0.11.3 is running fine here (amd64, just renamed the ebuild), but seems to have a regression with Python 2.3 and a few other small bugs ( http://trac.edgewall.org/query?group=status&milestone=0.11.4 ) 0.11.4 is supposed to be out in a few days - I'll update this bug if its released
trac 0.11.4 has just been released
renaming the .2 ebuild to .4 works fine here on amd64 (install & basic usage tested)
Confirmed working nicely here as well (python 2.5).
Manually bumping to .4 works for me too on ~amd64. Also, I'm using tracd instead of mod_python or similar.
I recently ran into an issue with trac-0.11.4 and subversion-1.6 where annotating source code causes an assertion error. Luckily upstream provides a working patch at http://trac.edgewall.org/ticket/8179 But if trac-0.11.4 is to be added to the portage tree I think this patch must be applied, or wait for the next release.
Thanks for the note David. I was just about to hack manually and get .11.4, but will hold off for now.
I have an ebuild in my overlay for 0.11.4 with upstream's patch for upstream #8179 (taken from upstream r8015, author Christian Boos). http://hg.xavamedia.nl/portage/raw-file/0466926ca33e/www-apps/trac/files/svn-1.6-annotation-0.11.4.patch http://hg.xavamedia.nl/portage/raw-file/tip/www-apps/trac/trac-0.11.4.ebuild
I found a need for trac on my own server. Will see if i can do something to it today. Anyone using 0.11.5 and still getting that assertion error? @webapps: any chance of this being bumped in the tree?
(In reply to comment #10) > Anyone using 0.11.5 and still getting that assertion error? No, the upstream fix is included in 0.11.5.
As before: renaming the 0.11.3 ebuild to 0.11.5 works for me (amd64, lighttpd) No dev with a trac installation around to bump?
Fixed.
