Hello Roger, First, the thing is still called "trac" not "tracs" even if it now supports multiple repositories ;-)
Roger O wrote: > I am considering updating my tracs install from the 0.12 multirepos > from 2008-09-09 (when I installed it was current at the time) to the > current version. Although I use tracs daily, I do not update so very > often. Is there a guide to doing this correct? Would these steps be > adequate: > > - Stop tracs logins > - Back up current tracs env > Yes. > - Back up the tracs parts in /usr/lib/python/site-packages/ > Trac-0.12multirepos-py2.5.egg, where I guess all of tracs lives. > Well, that step is not really needed (you can always checkout an earlier version if things go bad). A good habit is to make a note somewhere about which revision was in use before you do a "svn update" (e.g. you can do: "svn info >> LAST_STABLE; svn update"). > - Install the new 0.12 multirepos tracs from svn > Also do: trac-admin <tracenv> upgrade as there has been a schema change recently (the repository cache now supports multiple repositories as well). However, we also plan to do a schema change very soon on trunk, and this will actually conflict with the schema change we did on the branch. So if you don't want to have to mess with the db manually, better wait a few more days until we merge the upcoming trunk change into the multirepos branch (I'll follow up here when it's done). > - Check for any diffs in the tracs.ini file > There shouldn't be currently, but yes, good idea (comparing your trac.ini with the trac.ini.sample file written after the trac-admin update). > - Enable tracs logins > - Enjoy > Also do: trac-admin <tracenv> help repository In order to learn about the new commands. New hook scripts will be coming soon. > One thing that made me stop and ask this question was that I see I > have an older tracs in /usr/lib/python/site-packages/Trac-0.11.1- > py2.5.egg. I remember starting with this one and then later upgrading > to 0.12 multirepos, but I do not recall what I did to make > Trac-0.12multirepos-py2.5.egg be used instead of Trac-0.11.1- > py2.5.egg. Age... After installing the new 0.12 multirepos, should I > need to do anything to get it to be used? Based on the names I see, I > am guessing the update will replace the existing Trac-0.12multirepos- > py2.5.egg. > The /usr/lib/python/site-packages/easy-install.pth file contains the reference to the active version. When you do a python setup.py install, it takes care of updating that file, so you don't have to bother. > I have been following the development of tracs and see that there are > new features being added that would make my tracs experience even > better (things like render user variable text, use user variable > descriptions instead of the variable name as labels). You mean the wiki custom fields... Yes, the multirepos is usually quite in sync with trunk, so you'll have this as well. > Is it the plan > that the multirepos branch be fully merged with the trunk so it gets > all these nifty new features? Or will the multirepos remain a branch? > The integration in trunk will happen at some point, but the target has not been formally decided yet. Things are progressing well enough so that it seems plausible to have it in Trac 0.12. > Just curious. No problem, thanks for your interest! -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
