Status of FOM as I head off to bed

[Jason Molenda <jason-swarelist@molenda.com>]

Still no joy.

I had to upgrade from 2.709 to 2.717 for it to work correctly with
perl 5.6.1.  Each of the existing databases --

  cgen
  sid
  ecos
  gcc

is currently inaccessible until the maintainer of each goes to some
"install" page.  I've asked jifl, the maintainer of the ecos
database, to see if he can get to that install page.  If that
doesn't work for him, I'll see about forcing new admin passwords
or whatever is necessary.

FOM stores hashes of each user's password in one of its config files.
In 2.709 these hashes were crypt() strings.  Now they're 128-bit
md5 hashes.  I _suspect_ that FOM will update the passwords as users
log in, but I don't know that for certain.  (I looked over all the
release notes foreach release and found no mention of this problem)

If anyone logs in as an admin, keep this caveat from one of the
release notes in mind for that first install-login:

  WHEN YOU UPGRADE TO 2.714, YOU MUST BE CERTAIN TO PASS THROUGH
  THE "Define Configuration Parameters" PAGE.

  You shouldn't have to actually define any parameters; the defaults
  are fine if you use GNU RCS. But you must pass through that page
  to get the args defined; otherwise RCS will get called with empty
  options and will end up making a mess of things. (A reversible
  mess, but a mess nonetheless.)

  If, when you upgrade, you consistently follow the directions (go
  to the installer page and check off the newly-unchecked boxes),
  you'll be fine. I discovered this problem because I cheated and
  just checked the "Mark the config file as upgraded" box, to make
  the "admin must run installer" message go away. :v)