I got this:
$ cvs checkout amber11
woods.loyd.scripps.edu's password:
cvs server: Updating amber11
cvs server: failed to create lock directory for `/thr/loyd/case/cvsroot/amber11' (/thr/loyd/case/cvsroot/amber11/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository `/thr/loyd/case/cvsroot/amber11'
cvs [server aborted]: read lock failed - giving up
...but
$ cvs checkout amber10
seems to be working.
I know very little about CVS, so I have no idea how to interpret this.
:-) Lachele
--
B. Lachele Foley, PhD '92,'02
Assistant Research Scientist
Complex Carbohydrate Research Center, UGA
706-542-0263
lfoley.ccrc.uga.edu
----- Original Message -----
From: David A. Case
[mailto:case.scripps.edu]
To: amber-developers.scripps.edu
Sent: Wed, 16 Apr
2008 13:56:42 -0400
Subject: amber-developers: amber11 CVS is now open
> As we have done in the past, the amber10 cvs tree is now closed, but I
> have prepared an amber11 module for future development. (The naming scheme
> is
> maybe odd, but consistent with past practice: this is what will *eventually
> become* Amber 11. For right now, it is the same as Amber10.)
>
> * get it by "cvs checkout amber11"
>
> * All CVS revision numbers have been brought up to a common 10.0.
>
> * I removed things that I thought were not necessary going forward. If
> something is missing that needs to be there, please let me know (or add
> it in yourself.
>
> * I think that everyone who had commit access to amber10 can no commit to
> amber11. Anyone I missed was not deliberate! Just let me know if your
> karma is insufficient.
>
> * As with amber10, the amber11 CVS tree also contains the current
> AmberTools
> codes. So, if you have updates or corrections to those codes, put them
> in amber11 CVS. But also post bugfixes to the Amber web page.
>
> Thanks again to everyone for your hard work in getting AmberTools and
> Amber10
> out the door!
>
> ...regards...dave
>
>
Received on Fri Apr 18 2008 - 21:19:52 PDT