svn-migration-scripts.jar authors fails with ssh connection (svn+ssh)

[Robert Muil]

Running the migrations script to export authors fails when the repository connection is over ssh/svn protocol:

java -jar ~/svn-migration-scripts.jar authors svn+ssh://<repourl>

gives:

About to create the authors file.

Invalid svn command

[Carlos Rueda]

Just hit this very issue. Is there any workaround?

[Carlos Rueda]

Thanks for the link Jase. Yes, basically I simply ran `svn log --quiet | awk '/^r/ {print $3}' | sort

[jimmies]

I had similar solution make sure your repository in the command is terminated with a forward slash : repository/

[Tom Liu]

have same issue with svn+ssh here

[joyous javadev]

I had same issue and as jimmies suggested, this is how I resolved it. After your svn repository path ends, follow it up with forward slash and your SVN repository name

On Windows, D:\java>java -jar svn-migration-scripts.jar authors file:///D:\your\svnrepositorypath/yourSVNrepositoryname > authors.txt

[sidner]

Having the same problem on Linux. Any solution? Tried the "adding the project at the end" suggestion, didn't work.

[B Cherkezov]

Having the same problem here. Adding the forward slash didn't help.

My tools versions:

svn-migration-scripts: using version 0.1.56bbc7f

Git: using version 1.7.9.5

Subversion: using version 1.6.17

git-svn: using version 1.7.9.5

[Joel C Forster]

I'm having the same issue. Adding the slash has had no effect.

Has anyone made any breakthroughs on this?

[Kevin Nagurski]

Having the same issue here.

[Morjan Mihail]

Any solution for this?

[Kevin Nagurski]

Best solution I found was to abandon it and go for svn2git instead. Must easier and better supported.

[Morjan Mihail]

There are problems too. For example the password can't be inserted as parameter anymore from terminal and when I enter the password can't trigger the enter anymore. Hardly solved the problem by setting the first imput from a file. Now I have problems with the branches... This problem is a bit too old and is well known, why nobody can't support this issue?

[Dale Cooper]

On Unix this will work. Similar should work on Windows. Create a shell script called svn. In that file simply set up your subversion PATH LD_LIBRARY_PATH etc and on the last line ...

svn_client_distro_path=/some/path/or/other/svn_client
PATH=$svn_client_distro_path/bin:$PATH
LD_LIBRARY_PATH=$svn_client_distro_path/lib:$LD_LIBRARY_PATH
export PATH LD_LIBRARY_PATH
#  BE CAREFUL you must use a path to the svn binary/app, otherwise you stand a chance of recursively calling this svn hijack script and killing your host.
set -vx ; $svn_client_distro_path/bin/svn --username=bert --password=erniesnores "$@"

Then ensure that the svn hijack script is in your PATH, ahead of the real svn path. That way you hijack the call to svn and inject your own switches. The set -vx allow you to see what other switches are being used.

[John Reimers]

This worked for me on OS X (using https):

java -jar ~/svn-migration-scripts.jar authors <svn-repo> username password > authors.txt

Just make sure your <svn-repo> (https://path) is the svn root. It may take a few minutes if your repo is large.

[sucotronic sucotronic]

Bad ugly workaround:

• create local mount point

   mkdir /tmp/svn_repo

• mount over sshfs

   sshfs username@repo_url.com:/path/torepo /tmp/svn_repo

• execute the script over local mount point

   java -jar svn-migration-scripts.jar authors file:///tmp/svn_repo/svn_path > authors.txt

[mattack1]

We're using svn+ssh://

Is that the reason I'm getting this error? Is there a workaround?

Well, I got it to not error out, but it didn't make any progress. The difference was that it needed username after the repo.. e.g.

java -jar ~/svn-migration-scripts.jar authors svn+ssh://REPO/ USERNAME > authors.txt

but again, that actually didn't work for me, it just didn't error out..

What DID work was this: svn log --quiet | grep "^r" | awk '{print $3}' | sort | uniq I'm not sure if that's really all I need.