subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bo Berglund <bo.bergl...@gmail.com>
Subject Re: First cvs2svn conversion, problem with "symbols"
Date Fri, 08 Dec 2017 15:37:48 GMT
On Fri, 08 Dec 2017 12:24:19 +0100, Bo Berglund
<bo.berglund@gmail.com> wrote:

>What am I missing? It seems like the symbol handling defined in the
>options file is not used....

I ended up putting the following into the options file where the
sub-projects are defined:

import os
cvs_repo_main_dir = '/home/bosse/CVSREPOS/Bosse'
projects = os.listdir(cvs_repo_main_dir)
projects.remove('CVSROOT')
for project in projects:
    run_options.add_project(
        cvs_repo_main_dir + '/' + project,
        trunk_path=(project + '/trunk'),
        branches_path=(project + '/branches'),
        tags_path=(project + '/tags'),
		symbol_strategy_rules=global_symbol_strategy_rules,
        )

Note teh last line, which seems to be necessary for the default rules
to be applied....

Anyway, now I got past the early symbol parsing error and wound up
here:

----- pass 16 (OutputPass) -----
Starting Subversion Dumpfile.
Starting Subversion r1 / 855
Starting Subversion r2 / 855
ERROR: The command '/usr/bin/cvs -Q -R -f -d
:local:/home/bosse/CVSREPOS/Bosse co -r1.1.1.1 -p -kb
cvsweb/cvsweb.cgi' failed with exit status=1
and the following output:
cvs checkout: connect to 127.0.0.1(127.0.0.1):2402 failed: Connection
refused
cvs [checkout aborted]: Couldn't connect to lock server

This error is strange since it implies that cvs2svn is trying to
access the cvs *server* to do some checkout, which of course will fail
miserably since the documentation specifically states that cvs2svn
MUST operate on the CVS repository files directly!

And it also states that one should make a *copy* of the repository
files for cvs2svn to operate on! So my files are not a real repository
served by a server at all.

What gives?
Is there some option inside the options file which needs to be set to
declare that the cvs access is by way of direct file manipulation
using the cvs *executable* rather than a service?
This is what I have used in the options file:

ctx.revision_collector = NullRevisionCollector()
ctx.revision_reader =
CVSRevisionReader(cvs_executable=r'/usr/bin/cvs')

Please shed some light on this!
It seems like I am really close and yet not there at all....


-- 
Bo Berglund
Developer in Sweden


Mime
View raw message