All I do is note the rev that I'm currently using. Since you are using
subversion its easy enough to put the working copy to any rev you want
(svn up -r). If you need to go back the just
delete /usr/lib/python2.3/site-packages/trac and do a python stup.py
install from your reverted directory to reinstall everything fresh. This
has always worked for me and I think its fine unless there is a DB
version change somewhere.
THere are probably lots more anal ways to do it but I've managed to flip
back and forth a few times like this.
Greg
On Thu, 2006-12-21 at 11:16 -0500, Gary Oberbrunner wrote:
Hi; I'm currently using trac SVN r3790 (from Sept. 25). At that point it was
working well, and we were in crunch mode so I didn't want to touch it.
I'd now like to update to the latest trunk to get the latest good stuff and be
prepared for the upcoming wonderfulness (blame, workflow, etc.).
My question is, since trac is in daily use (3 developers), how can I make 100%
sure I can go back to my existing version if my upgrade goes bad?
I know I should start with this:
trac-admin /path/to/trac/projenv hotcopy ~/trac-backup.
But what about the Python modules in my python site-packages, the stuff in
/path/to/trac (i.e. one level above my projenv), and is there anything else I
might need to put back? I'm using SQLite and svn backend, btw.
(I'm partly worried that some plugins might stop working; webadmin, tractags,
graphviz? But mostly I just want to make sure trac doesn't completely break.)
Thanks,
-- Gary
>
--
Greg Dickie
just a guy
Maximum Throughput
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
