Jim Meyering wrote:
> I've set up for cvs pserver (read-only) access to the git mirror
> of gnulib's cvs repository. This is in preparation for discontinuing
> the CVS repository in favor of the git one for upstream commits.
>
> To check out the latest, use this:
> cvs -d :pserver:[EMAIL PROTECTED]:/gnulib.git co -d gnulib HEAD
The previous cvs access to gnulib was:
$ cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/gnulib checkout gnulib
That cvs access is still available. But it is now getting stale.
$ awk '{print$1;exit}' gnulib/ChangeLog
2007-09-18
If the old cvs access is not going to be updated then let's disable it
so that those attempting to pull the previous cvs path will get an
error instead of old data. Disabling it so that an error is reported
would be good and would have saved me a small amount of debugging.
I am not going to be using the cvs access further but I was happy to
let the buildbots run from them for a bit longer. No errors were
being reported. I am sure others will be in the same mode and will
have stale cvs repositories laying around and updates will work but
the latest update will be the stale data. If they had started
producing errors I would have caught this problem sooner and would
have known that changes were happening.
In case someone wants to keep using a cvs working copy and simply
wants to convert to the new cvs access location the following should
convert the cvs working copy in place from the old cvs depot to the
new cvs-access-to-git depot.
find . -name Root -exec sed --in-place 's|[EMAIL
PROTECTED]:/cvsroot/gnulib|[EMAIL PROTECTED]:/gnulib.git|' {} +
find . -name Repository -exec sed --in-place
's|gnulib|/srv/git/gnulib.git/HEAD|' {} +
That worked for me on my old cvs working copy. And then I removed my
cvs working copy since I have converted everything over to git for all
future checkouts. :-)
Bob
