search

fourjay / vcscommand

Automatically exported from code.google.com/p/vcscommand
0 stars 0 forks source link

No suitable plugin with SVN 1.7.3 #96

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
1. version 7.3
2. SVN 1.7.3
3. Linux OS
4. vcscommand-1.99.46

Any VCScommand returns follwing error.
VCSCommand: No suitable plugin

I can see latest SVN path in my $PATH.
In xterm all svn commands are working fine.

Any pointers will be really helpful

Original issue reported on code.google.com by bsandee...@gmail.com on 16 Mar 2012 at 3:49

GoogleCodeExporter commented 8 years ago 
Are you using vim or gvim?  If gvim, are you sure your path contains svn?

From within (g)vim, try the following:

:!svn info .

Original comment by bob.hies...@gmail.com on 21 Mar 2012 at 1:44

GoogleCodeExporter commented 8 years ago 
Hi,
Thanks for your reply.
I use GVIM. 
I tried the above command within the gvim.
 and i get the following message:

svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy rooted at '<root dir path>'.
Please upgrade your Subversion client to use this working copy.

How can I resolve it?

Original comment by bsandee...@gmail.com on 21 Mar 2012 at 6:54

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Thanks for the reply.
Now SVN log, svn diff, svn info commands work properly.
However when I try to check-in my changes i get the following error.

"VCSCommand:  Version control command failed:  svn: symbol lookup error: svn: 
undefined symbol: svn_opt__eat_peg_revisions"

Original comment by bsandee...@gmail.com on 12 Apr 2012 at 8:08

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
You seem to be using an older SVN client to access a repository checked out by 
SVN 1.7.  You may want to upgrade your local SVN or make sure you use the right 
one, if you have more than one installed.

Original comment by bob.hies...@gmail.com on 12 Apr 2012 at 3:53

GoogleCodeExporter commented 8 years ago 
You get the 'No suitable plugin' message even with the proper client and the 
proper working copy versions.

VCSCommand (actually vcssvn.vim) tries to find the .svn/ subdirectory in the 
directory of the currently opened file.

However in svn 1.7 this .svn/ dir only exists in the root of the working copy, 
and is no longer found in subdirectories within the wc.

Original comment by terminatorul@gmail.com on 12 Apr 2012 at 4:20

GoogleCodeExporter commented 8 years ago 
You should not get that with version 46 of the plugin, which the reporter 
referenced.

Original comment by bob.hies...@gmail.com on 12 Apr 2012 at 6:34

GoogleCodeExporter commented 8 years ago 
Yes, that is correct. Sorry, I had an old version.

Original comment by terminatorul@gmail.com on 13 Apr 2012 at 11:27

GoogleCodeExporter commented 8 years ago 
Thanks for the hint [Comment6]. It works for me now. Thanks very much for your 
support.

Original comment by bsandee...@gmail.com on 13 Apr 2012 at 12:27