using rsync to create local repository

using rsync to create local repository

[PAUL GILLIAM]

Hi,

In order to use Janus Johnson's cool binary patch finder, I need to
create a local copy of GDB's cvs repository.

Her patch finder does a binary search through the patches find the one
that breaks or fixes what you are interested in.  For each patch
examined, a source tree is updated, the project is built and a test
script is run to see if whatever is broken or fixed.

Although it's possible to do this with a remote repository, the time
needed for cvs updates (not to mention the network traffic) would be
prohibitory.

For Janus' GCC testing, she uses the following command to create and
update a local copy of the cvs repository:

rsync --archive --delete --compress --progress \
      --exclude '#cvs.*' --exclude 'CVSROOT/config' \
      --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
      rsync://gcc.gnu.org/gcc-cvs gcc-cvs

I tried a similar thing and it seemed to work:

rsync --archive --delete --compress --progress \
      --exclude '#cvs.*' --exclude 'CVSROOT/config' \
      --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
      rsync://sources.redhat.com/gdb-cvs /home/pgilliam/gdb/gdb-cvs

But when I tried to do a checkout, I got this:

[pgilliam@dufur test]$ cvs -d /home/pgilliam/gdb/gdb-cvs/ co gdb
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-texinfo' in modules file contains infinite
loop
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-texinfo' in modules file contains infinite
loop
cvs checkout: module `naked-bfd' in modules file contains infinite loop
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-texinfo' in modules file contains infinite
loop
cvs checkout: module `naked-bfd' in modules file contains infinite loop

... and so on


Any ideas on what I am doing wrong?

Thanks for your help,

-=# Paul Gilliam #=-

Re: using rsync to create local repository

[Daniel Jacobowitz]

On Thu, Jan 26, 2006 at 10:56:28AM -0800, PAUL GILLIAM wrote:
> I tried a similar thing and it seemed to work:
> 
> rsync --archive --delete --compress --progress \
>       --exclude '#cvs.*' --exclude 'CVSROOT/config' \
>       --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
>       rsync://sources.redhat.com/gdb-cvs /home/pgilliam/gdb/gdb-cvs

Wrong repository.  You want src-cvs, not gdb-cvs, which only has the
web pages in it.

-- 
Daniel Jacobowitz
CodeSourcery

Re: using rsync to create local repository

[PAUL GILLIAM]

On Thu, 2006-01-26 at 14:07 -0500, Daniel Jacobowitz wrote:
> On Thu, Jan 26, 2006 at 10:56:28AM -0800, PAUL GILLIAM wrote:
> > I tried a similar thing and it seemed to work:
> > 
> > rsync --archive --delete --compress --progress \
> >       --exclude '#cvs.*' --exclude 'CVSROOT/config' \
> >       --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
> >       rsync://sources.redhat.com/gdb-cvs /home/pgilliam/gdb/gdb-cvs
> 
> Wrong repository.  You want src-cvs, not gdb-cvs, which only has the
> web pages in it.
> 
Ahhh.  That would explain it.

Would it be useful for me to submit a patch that would add this
information to one of those web pages?

Thanks for the help,

-=# Paul #=-

Re: using rsync to create local repository

[Daniel Jacobowitz]

On Thu, Jan 26, 2006 at 12:53:40PM -0800, PAUL GILLIAM wrote:
> On Thu, 2006-01-26 at 14:07 -0500, Daniel Jacobowitz wrote:
> > On Thu, Jan 26, 2006 at 10:56:28AM -0800, PAUL GILLIAM wrote:
> > > I tried a similar thing and it seemed to work:
> > > 
> > > rsync --archive --delete --compress --progress \
> > >       --exclude '#cvs.*' --exclude 'CVSROOT/config' \
> > >       --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
> > >       rsync://sources.redhat.com/gdb-cvs /home/pgilliam/gdb/gdb-cvs
> > 
> > Wrong repository.  You want src-cvs, not gdb-cvs, which only has the
> > web pages in it.
> > 
> Ahhh.  That would explain it.
> 
> Would it be useful for me to submit a patch that would add this
> information to one of those web pages?

I suppose.

-- 
Daniel Jacobowitz
CodeSourcery