On Fri, 2004-07-09 at 09:22, Raymond Toy wrote:
> While trying to do a cvs update so I can check in a fix, I'm getting
> the error:
>
> cvs [update aborted]: read lock failed - giving up
> Parser Error: 'cvs update: failed to create lock directory for `/cvsroot/maxima/maxima' (/cvsroot/maxima/maxima/#cvs.lock): Permission denied'
> Parser Error: 'cvs update: failed to obtain dir lock in repository `/cvsroot/maxima/maxima''
>
> Is it something on my end or with sourceforge? (I'm not doing anon
> cvs access.)
I see the same behavior. Sourceforge has had many temporary problems
like this. In fact, they are currently upgrading cvs, so this may be a
glitch in the process. (See the Sourceforge site update at the end of
this message.)
I'll file a support request if the problem doesn't clear up soon.
--Jim
Sourceforge site update:
( 2004-06-24 10:20:28 - Project CVS Service ) As per the 2004-05-31
site mailing, the SourceForge.net team is working to complete our second
major CVS infrastructure upgrade (the first was done more than a year
ago). This infrastructure upgrade will eliminate the delay between
developer and non-developer CVS (presently a 5 hour sync delay). In
coming weeks, a significant amount of new hardware will be installed and
other service enhancements will be rolled out. This notice is being
posted to alert you to our revised schedule. We are confident that the
end-product will exceed the performance requirements we originally
devised. This upgrade is happening in pieces; new features and fixes are
already being rolled out. The hardware cutover will occur at the end of
this upgrade process (we are waiting for the replacement hardware to
arrive). To monitor the progress of this project, please watch Site Doc
I9 for announcements.