I would start by backing up the database, pulling down latest trunk, and seeing if you can migrate up to it. Some time ago a lot of work was done on the migrations to try and make it as robust as possible, so it should be a lot better now.

If that fails, come back and ask again.

On May 6, 2006, at 10:34 AM, Hal Fulton wrote:

I've been putting this off but eventually I'll have to
bite the bullet.

My Typo is old. So old I'm not sure how old. So old I'm
not even sure how to find out what version I have.

I notice some things like test/ are timestamped Oct 5.

I do remember I was updating it from svn -- I also remember I
had migration issues every single time I migrated, and I had
no custom code or anything.

If you were me, where would you start? Besides backing up
the database, that is.

--
Kevin Ballard
[EMAIL PROTECTED]
http://kevin.sb.org
http://www.tildesoft.com


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

Reply via email to