Marko Käning wrote, On 08/19/2008 10:35 AM:
Hi Todd,
In my description I used paths which would be used with -d option on
checkout.
<SNIP establishment that we are talking about data directories and not the
control dir.>
Well, of course I wanted to keep the HISTORY! ;)
{I am almost betting you are going to send another message indicating you were
talking more about $CVSROOT/MyVersionControlledDataDirectory instead of the
$CVSROOT/CVSROOT/module module name control file, but I am going to make you
send it, i.e., if you meant something other than $CVSROOT/CVSROOT/module you
should have not have abstracted as much.}
Well, I meant of course the $CVSROOT/MyVersionControlledDataDirectory. The
module named module was a bad choice for this example, I see... Well, and
here it is, my other message you made me send... ;)
In this case, doing a cp of the data should work with out problem, as this is
just a special case of "Backing up a repository"[1].
did your convert work BEFORE you did the copy?
Have you asked the mercurial convert program author for help?
Not yet, at first wanted to make sure that I am not messing up my CVS repo
by doing so, before I contact the convert author.
You might be able to get a little more information if you turn some debugging
on...
I suggest reading the docs about the mercurial convert program and see if it
has some debugging or verbose flags you can set, and you could probably set
the cvs option for tracing[2] or set $CVS_CLIENT_LOG [3] to see if it
mercurial is getting data by using cvs (you might have to set tracing in the
cvsrc file).
For the URLs below, please download
http://ftp.gnu.org/non-gnu/cvs/source/stable/1.11.22/cederqvist-1.11.22.html.tar.bz2
to your home directory and put a copy of it in /tmp.
cd /tmp
tar -xjvf cederqvist-1.11.22.html.tar.bz2
[1] file:///tmp/cederqvist-1.11.22.html/cvs_2.html#SEC24
[2] file:///tmp/cederqvist-1.11.22.html/cvs_16.html#IDX211
[3] file:///tmp/cederqvist-1.11.22.html/cvs_19.html#SEC185
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
