forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@lyra.org>
Subject Re: forrest cvs->svn
Date Fri, 12 Mar 2004 00:27:55 GMT
On Wed, Mar 10, 2004 at 12:48:37PM +1100, David Crossley wrote:
>...
> > > I presumed that "read-only" meant that i could still do 'cvs update'
> > > but it seems that i cannot. Is that the intended behaviour?
> > > 
> > > ------
> > > cvs server: failed to create lock directory for `/home/cvs/xml-forrest'
> > > ...
> > 
> > That was not the intent, but it is an unfortunate side-effect of the way
> > CVS works (unless we're using LockDir, which we're not).

Just toss people out from the 'avail' file. That will disable commits to
the repository. Then make the module directory writable again, which will
allow for lockfiles to be created.

> > What would the Forrest committers like to do?  We could just flip it
> > back to read-write if all the committers know that anything they commit
> > to CVS is effectively going into the bitbucket.
> 
> Many thanks for your explanation and for your work on this.
> 
> Please leave it as "read-only" for the moment. We will talk
> about it on forrest-dev@ and get back to infrastructure@ later
> if we want anything different.

How does the above sound?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Mime
View raw message