[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Wed, 2009-04-01 at 20:27 +0200, Christian Boos wrote: 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). I am finally getting ready to update from a very old Trac 0.12multirepos to something more up-to-date. Is the only source of an update via svn? Or is there a checked out version that would be safer to use? I figure it is better to ask than to be sorry. -- Roger Oberholtzer --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
Roger Oberholtzer wrote: On Wed, 2009-04-01 at 20:27 +0200, Christian Boos wrote: 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). I am finally getting ready to update from a very old Trac 0.12multirepos to something more up-to-date. Is the only source of an update via svn? Or is there a checked out version that would be safer to use? I figure it is better to ask than to be sorry. The current 0.12 multirepos has inherited a few quirks from trunk which are now fixed - but only in trunk. I'll sync the branch later today, and with that version, you should be fine ;-) -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
Silly question, but which trunk is being updated?http://svn.edgewall.org/repos/trac/trunk? Gee, it was a dumb question, as I got no response. The reason I asked was that the multirepos was in a 0.12 branch. But, is it the case that the changes in 0.12multirepos are now going in the earlier numbered 0.11 series? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Apr 14, 1:46 pm, Christian Boos cb...@neuf.fr wrote: Nearly there. The new schema is in place and the cache is working, together with the new hook (contrib/trac-svn-hook). Only a few rough edges need to be polished (seehttp://trac.edgewall.org/ticket/7723for details), but it's already working and an upgrade should be safe at this time. Silly question, but which trunk is being updated? http://svn.edgewall.org/repos/trac/trunk? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Apr 1, 8:27 pm, Christian Boos cb...@neuf.fr wrote: 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). Just curious how it's going? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
Roger O wrote: On Apr 1, 8:27 pm, Christian Boos cb...@neuf.fr wrote: 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). Just curious how it's going? Nearly there. The new schema is in place and the cache is working, together with the new hook (contrib/trac-svn-hook). Only a few rough edges need to be polished (see http://trac.edgewall.org/ticket/7723 for details), but it's already working and an upgrade should be safe at this time. The new documentation page about multiple repository management is still to be written, but the trac-svn-hook script should contain enough inlined documentation to get you started. -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Tue, Apr 14, 2009 at 01:46:15PM +0200, Christian Boos wrote: Roger O wrote: On Apr 1, 8:27 pm, Christian Boos cb...@neuf.fr wrote: 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). Just curious how it's going? Nearly there. The new schema is in place and the cache is working, together with the new hook (contrib/trac-svn-hook). Only a few rough edges need to be polished (see http://trac.edgewall.org/ticket/7723 for details), but it's already working and an upgrade should be safe at this time. The new documentation page about multiple repository management is still to be written, but the trac-svn-hook script should contain enough inlined documentation to get you started. Any interest in making the svn-hook (and potentially other hooks) pluggable entry points a la http://trac-hacks.org/wiki/RepositoryHookSystemPlugin or [deprecated] http://trac-hacks.org/wiki/SvnChangeListenerPlugin? Jeff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Tue, Apr 14, 2009 at 04:36:00PM +0200, Remy Blank wrote: Jeff Hammel wrote: Any interest in making the svn-hook (and potentially other hooks) pluggable entry points That's already done. Look at the IRepositoryChangeListener interface in trac.versioncontrol.api, and the new trac-admin $ENV changeset (added|modified) commands. I have also rewritten the previous post-commit hook that added comments to tickets as a plugin implementing IRepositoryChangeListener, see sample-plugins/commit_ticket_update.py. -- Remy Cool! I look forward to deprecating my plugins :) Jeff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Apr 1, 8:27 pm, Christian Boos cb...@neuf.fr wrote: Also do: trac-admin tracenv upgrade I am guessing I did this last time. It looks familiar. 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. Could be the same thing. You mean ticket custom fields that are treated like wiki text (like the ticket description)? 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. I use the multirepos for the obvious reason. But I do have a 'parent' repository that has some glue, and all the repositories as externals. An alternative would be if Trac support extarnals. I am guessing not. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Thu, Apr 2, 2009 at 12:20 AM, jevans jevans...@gmail.com wrote: On Apr 1, 1:27 pm, Christian Boos cb...@neuf.fr wrote: Roger O wrote: 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 That would be awesome Agreed. We've been running multirepos since around June on an internal production Trac (currently at Trac 0.12multirepos-r7684) with a couple svn and a whole Mercurial forest. It would be great to get it out, as I know a bunch of users could benefit from it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
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 trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Upgrading existing tracs 12 multirepos to a newer version
On Apr 1, 1:27 pm, Christian Boos cb...@neuf.fr wrote: Roger O wrote: 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 That would be awesome --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
