Wed 10 October 2007
Filed under Blogs
Typo has seemed a little off lately. Last night I finally broke and upgraded. Typo 4.0.x => 4.1.1
pg_dump -U typouser -D typodb > 2007-10-09.typo.dump createdb -U pgsuper -U typoeuser -D typodbnew Welcome to psql 8.1.5, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit typodbnew=> \i 2007-10-09.typo.dump
Now I used Portage to update all of the various rails and ruby packages. This went swimmingly.
After the update, my old blog instance failed to run. *whoops*. I forget the error, and I don't really care. But note: It may be that with the latest Ruby and Rails packages, Typo 4.0.3 will have a problem.
I don't know how new it is, but it's new to me: The typo install command. The moral of this story boils down to this:
Run your updates from portage.
Install typo via gem
gem install typo
Copy typo to a new folder:
cp -aR ~/typo-jms-4.0.0 ~/typo-jms-4.1.1
The major problem came in that I never used the typo command before, after a lot of trial and error and a DROPPED DATABASE, I discovered this.