This morning I made my list of things wrong with my Windows installation. Recently, this list is:

1. Windows hangs and becomes unresponsive
2. On closing Windows, an error message comes up that I don’t recognize
3. Deleting files takes forever and sometimes crashes my system

I’ve got to figure out the first two, but I’ve figured out the last. Deleting a file would try to put the file in my recycling bin, but my recycling bin was a bit on the large size and needed to be emptied. After clearing it out, everything is running smooth. Now, I’ve got to fix the first two.

With Rails 2.0 out now, it’s time to explore the new source. It’s hard to believe that it’s already been 2 years since I first checked out Rails 1.0 for the first time.

To update your Rails code, you can run
gem update rails

However, when I tried to run this command I was unfortunately greeted with a nasty error, when getting to update ActiveRecord.

Attempting remote update of activerecord
ERROR: While executing gem ... (Zlib::BufError)
buffer error

According to a Ruby Form post, I found a solution to the problem, updating ruby gems.

While you could run this line to update RubyGems to 0.9.5, I don’t recommend it.
gem update --system

Instead download rubygems-0.9.4, unzip it and then run
ruby setup.rb

This will allow you to continue to use Mongrel, because there are some incompatibilities with Mongrel running on Win32 with RubyGems 0.9.5. See the following:

• justaddwater.dk blog
• Ruby Forum Topic: Mongrel install crash on win32

and then update rails as you would expect.
gem update rails

Voila!

While moving a subversion repository from one location to another is an infrequent task, it’s good to know and easy to do.

According to dot not

svnadmin dump /path/to/repo > reponame.dump
tar zcf reponame.tgz reponame.dump
scp reponame.tgz hostname:/path/to/new/repo

Then login to the new machine, and set up the new repo:

cd /path/to/new
svnadmin create reponame
tar zxf reponame.tgz
svnadmin load reponame < reponame.dump

Voila, you have moved your repository. Don’t forget to delete your old repository when you have made sure that you are correctly referencing your new repository. Thanks Scott for the help.