I was attempting to migrate a Subversion repo to GIT and received this error…
error: 1024
error: Unexpected error has occurred; please report along with the logs (‘D:\ATLASSVN\GeoMaster\subgit-import-20210727-153011.zip’)
error: to https://support.tmatesoft.com/, thank you!
thank you for reporting this issue.
May I ask you what type of authentication is used for ssh? Is that key-based authentication and if yes what is the private key type format, PEM (RSA) or OPENSSH format?
this looks to be an SSH agent issue. May I ask you to try stopping and unloading the Putty agent (pageant.exe) and also try to unset the SSH_AUTH_SOCK environment variable if it’s set.
I agree is seems SSH related. I unloaded pageant and removed a SVN_SSH environment variable (set to C:\Program Files (x86)\PuTTY\plink.exe). No sign of a SSH_AUTH_SOCK env variable. Opened a new elevated command prompt and ran:
Haha! … might have it sorted. I grabbed the generated config file from D:\GIT\GeoMaster\subgit and copied it to D:\ATLASSVN\GeoMaster.
I edited to ensure that in the [SVN] section the url was set correctly and auth was set at default: url = svn+ssh://threadgillj@svn.integral.co.nz/repo/GeoMaster auth = default
In the [auth "default"] section sshKeyFile = D:/ATLASSVN/GeoMaster/threadgillj.pem useDefaultSubversionConfigurationDirectory = false subversionConfigurationDirectory = C:/Users/John/AppData/Roaming/Subversion
This section did not seem to be setup correctly.
Then ran this from D:\ATLASSVN\GeoMaster subgit import D:\GIT\GeoMaster
Seems to be busy “Translating Subversion revisions to Git commits…” :-)
that “Translating Subversion revisions to Git commits…” message indeed means that the import is in progress, so you are right, you have sorted that out! :)
As for the E170001 error – most probably this happened because the key has not been caught despite it was set as the command argument, we will investigate why could it have happened. The workaround is actually the approach with the preliminary configuration which you have applied)