-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration fails on directory links #40
Comments
@ycon123 It seems to be a problem of JGit handling links. We did out migration using a Llinux/Docker environment based on the rtc2git-docker based image, because we had RTC 5.0.2 at the time and needed to use an older version of JGit. What version of RTC are you using? |
I am executing the script with scmtools v5.0.2 (server v6.0.3) |
@ycon123 I see, could a migration within a docker container be an option for you? |
|
@ycon123 it seems that I do not understand exactly what you want me to say. I have no experiences with handling links during the migration from RTC to GIT jet, due the fact that we did not have such a scenario in our environment. I know, that handling links under Linux together with JGit could maybe working better than under Windows. It's just an assumption, not a proven fact. I would recommend you to give it an try using a docker image and try to migrate within that to see if that would fit your needs. (We did our complete migration this way, even though we where using Windows in our day to day work) If you like you could join the RTC to Git Slack Channel to chat with me later on. Just sign up under https://rtc.to/#slack |
Thanks! |
I suspect the migration fails because of a symbolic link problem (on Windows machine) - when the RTC repository contains directory/file links.
Is there a solution for this scenario?
Thanks!
The text was updated successfully, but these errors were encountered: