James Amundson <amundson@users.sourceforge.net> writes:
> On Fri, 2004-07-09 at 09:22, Raymond Toy wrote:
>
>> 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.
Is there any news on this? I haven't been able to update from CVS for
a month or so:
cvs up -Pd
cvs [update aborted]: connect to cvs.maxima.sourceforge.net(66.35.250.209):2401 failed: Connection timed out
--
Jesper Harder <http://purl.org/harder/>;