-
Notifications
You must be signed in to change notification settings - Fork 254
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
Fail on old repository #32
Comments
Duplicate of #34 |
I just ran into this with one of my projects. Same stack trace with export_file_contents, etc. No sanitize_name in the stack. |
In my case the crash was occuring in fast import because one of my branch names was problematic, even after being sanitized by sanitize_name. The imported repository had a branch named erroneously after a whole ssh:// URL, so something like: ssh://daniel@where-ever.com/repos/something The branch name was sanitized to replace the colon, but apparently the "/" also causes problems. I'll submit a pull request with a tweak to add / to the regex for sanitizing. This worked around the issue for me. |
Anybody else who comes across this issue, the right solution is to use the branch renaming -B flag to alleviate any problems that may be occurring because of the old Mercurial branch names. See explanation on #285. |
I have quite large repository. When I'm exporting to git from hg I'm receiving error:
I'm used following options:
../fast-export/hg-fast-export.sh -r reponame/ --hgtags --hg-hash --force
The text was updated successfully, but these errors were encountered: