As Mike indicated, your problem should be fixed by upgrading your courses to match the db modifcations.
To answer your specific question: the instuctions on the wiki will convert your codebase from a cvs checkout to a subversion checkout *of the trunk*. So you went from rel-2-4-patches (via cvs) to HEAD (via svn).
I think (and Mike or Arnie can confirm this) that the next numbered relase will be fairly soon and will be essentially what is now in the trunk. (And when people switch to that release they will need to do this course upgrade.)
Nevertheless, switching to the trunk is not what you expected - I'll update the instructions to make it more clear how stay in the rel-2-4-patches branch when converting (replace /trunk/ with /branches/rel-2-4-patches/).
Also, you can switch back from the trunk to the branch if you want. If you are going to try this, I'd recommend *not* upgrading the courses - only do that if you want to stay where you're at).
Here's how to do this:
- first verify that your working copy points to the trunk:
[jason@localhost pg]$ svn info | grep URL
- now do the switch:
svn switch http://svn.webwork.maa.org/system/branches/rel-2-4-patches/pg
The output will be a list of files changed as Subversion makes your working copy look like the current state of rel-2-4-patches.
Repeat for the webwork2 directory.
Once there is a branch for the next stable release, you can switch out of the trunk and into that branch like this also.
Hope this helps,