Bo:

I have been impacted by sourceforge split of the CVS server used for
development and the backup CVS server used to server requests.  The code
changes I was attempting to check in are now in the master CVS server.  It
may take 24 to 48 hours to see the updates on the public (backup) server.

SourceForge is temporarily running with the CVS services split between two
machines due to load issues.  Developers registered to a project can access
the primary server and perform updates.  Everyone else is currently
connecting to the backup server, which gets update once every 24 hours. 
[Update time is supposed to go down to every six hours shortly....] 
Sourceforge is working on a better solution (new hardware?) to get rid of
this problem....

Please re-synce (cvs update) with the cvs server.  Once you actually get
the updates, Squish will report a version number of 1.12 BETA....

Now to see if I can figure out how to automate the long command string I
need to use to access the developer server....  

Bob Jones, 1:343/41


 BJ> I've attempted to check in most of your suggested code 
 BJ> changes.  [I held off making the rescan change for 
 BJ> now.]  I also updated squish's version number to 1.12 
 BJ> beta for our testing purposes......

 BJ> Unfortunately, I still have something wrong with CVS.  
 BJ> On attempting to check in the files, after giving the 
 BJ> description of change, I get:

 BJ> cvs [server aborted]: "commit" requires write access to
the repository

 BJ> So, I still have something not setup correctly.  :(

 BJ> I'm still getting "cvs : CVSROOT "" must be an 
 BJ> absolute path name"
 BJ> error message near the startup of CVS.  :(

 BJ> Bob Jones, 1:343/41

 BJ> --- Maximus/2 3.01
 BJ> SEEN-BY: 343/41

--- Maximus/2 3.01