You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Dave Brondsema <da...@brondsema.net> on 2004/02/23 05:47:25 UTC

forrest cvs->svn

Forrest would like to move our source repository from CVS to Subversion.  We are
content with keeping history in CVS and starting with a "fresh" SVN repository
using the codebase from HEAD.  How do we proceed?

Thread with votes:
http://nagoya.apache.org/eyebrowse/BrowseList?listName=forrest-dev@xml.apache.org&by=thread&from=635927

Thanks!

-- 
Dave Brondsema 
dave@brondsema.net 
http://www.brondsema.net - personal 
http://www.splike.com - programming 
http://csx.calvin.edu - student org 

Re: forrest cvs->svn

Posted by Marshall Roch <ma...@exclupen.com>.
Dave Brondsema wrote:
> Forrest would like to move our source repository from CVS to Subversion.  We are
> content with keeping history in CVS and starting with a "fresh" SVN repository
> using the codebase from HEAD.  How do we proceed?

The timing on this couldn't be better... the Tigris server is currently 
being Slashdotted due to today's release of Subversion 1.0 (see the most 
recent story). :-D

--
Marshall Roch

Re: forrest cvs->svn

Posted by Juan Jose Pablos <ch...@che-che.com>.
David,

I sort it out using :pserver:anoncvs@cvs.apache.org/home/cvspublic

I hope this helps,
Cheers

David Crossley wrote:
> Brian W. Fitzpatrick wrote:
> <snip/>
> 
>>FYI, I've had Noel change the xml-forrest CVS repository to read-only.
> 
> 
> I am a Forrest committer and i tried to update my CVS working copy
> today, as i have some uncommitted changes and i also wanted to
> keep an up-to-date copy just prior to the SVN move.
> 
> 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'
> ...
> ------
> 
> --David
> 



Re: forrest cvs->svn

Posted by Eirik Bjørsnøs <bj...@stud.ntnu.no>.
>
> The following script might be useful. Please verify and improve the 
> messages, I just copied them from earlier postings:
>

Ok, this scfript would probably make ALL Apache projects read-only, but 
the script could easily be modified to hande that, since it gets a list 
of files to commit as input.

Eirik. :-)
-- 
Eirik Bjørsnøs
+47 41 46 37 65


Re: forrest cvs->svn

Posted by Eirik Bjørsnøs <bj...@stud.ntnu.no>.
> How about just adding a pre-commit script that simply returns false?
>
> This would allow checkout, release, update etc, but deny commits.
>
> Just a thought.

The following script might be useful. Please verify and improve the 
messages, I just copied them from earlier postings:

#!/usr/bin/sh
#
# svn-readonly.sh
#
# This program is used to deny commmits to the repository
# It is activated by adding the following line to CVSROOT/commitinfo
#   ALL $CVSROOT/CVSROOT/svn-readonly.sh
#
echo "The Forrest CVS repository is now read-only"
echo "Forrest now uses Subversion instead of CVS"
echo
echo "Checkout command:"
echo "svn co https://svn.apache.org/repos/asf/xml/forrest/trunk"
echo
echo "SVN Info:"
echo "http://incubator.apache.org/directory/svn.html"
echo
echo "Browse:"
echo "http://svn.apache.org/viewcvs.cgi/xml/forrest/?root=Apache-SVN"
exit 1

-- 
Eirik Bjørsnøs
+47 41 46 37 65


Re: forrest cvs->svn

Posted by Eirik Bjørsnøs <bj...@stud.ntnu.no>.
>> 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.

Hi,

How about just adding a pre-commit script that simply returns false?

This would allow checkout, release, update etc, but deny commits.

Just a thought.

Eirik.
-- 
Eirik Bjørsnøs
+47 41 46 37 65


Re: forrest cvs->svn

Posted by Greg Stein <gs...@lyra.org>.
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/

Re: forrest cvs->svn

Posted by David Crossley <cr...@apache.org>.
Brian W. Fitzpatrick wrote:
> David Crossley wrote:
> > Brian W. Fitzpatrick wrote:
> > <snip/>
> > > 
> > > FYI, I've had Noel change the xml-forrest CVS repository to read-only.
> > 
> > I am a Forrest committer and i tried to update my CVS working copy
> > today, as i have some uncommitted changes and i also wanted to
> > keep an up-to-date copy just prior to the SVN move.
> > 
> > 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).
> 
> 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.

--David



Re: forrest cvs->svn

Posted by David Crossley <cr...@apache.org>.
Brian W. Fitzpatrick wrote:
<snip/>
> 
> FYI, I've had Noel change the xml-forrest CVS repository to read-only.

I am a Forrest committer and i tried to update my CVS working copy
today, as i have some uncommitted changes and i also wanted to
keep an up-to-date copy just prior to the SVN move.

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'
...
------

--David