Chris Rorvick <ch...@rorvick.com>:
> I tried the new version and found I'm unable to import via pserver:
> $ ./cvsps --root :pserver:me@localhost:/cvsroot module
> cvsps: connect error: Connection refused
> cvsps: can't get CVS log data: Connection refused
> Running 2.2b1 (the version packaged w/ Fedora 17) with the same
> arguments with the addition of --cvs-direct connects OK. I haven't
> taken much time to look into this, so I might be doing something dumb.
> Thought I'd find out if this is a known issue before delving into it.
Your problem does reproduce here. This paragraph from the output of
'aptitude show cvs' may be relevant:
This package contains a CVS binary which can act as both client and server,
although there is no CVS dæmon; to access remote repositories, please use
:extssh: not :pserver: any more.
It's therefore possible there's something slightly busted about the pserver
method at the CVS end, and the 3. code trips over it even though the old
code did not. Note that new cvsps uses cvs-direct mode all the time; the old
support for fetching logs through local CVS commands is gone.
cvsps --root :local:$PWD/repo module
for my testing, and that works. I'm up to my ears in finishing up the
test suite and tracking bugs in the repo-analysis code; if you want to
speed the process up, try running a :pserver: fetch with -v on under
both old and new code to see how the protocol transactions differ.
> Also, I'm curious what impact removing the caching from cvsps will
> have on incremental imports. Is there any?
Not that I know of. The caching was a performance hack for human viewing
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html