-
Notifications
You must be signed in to change notification settings - Fork 86
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
Fix compatibility with Mercurial 3.2 #28
Conversation
if check_version(3, 2): | ||
return None | ||
else: | ||
raise IOError |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this for? I commented out this part and it still works fine for me. Could you refer to the Mercurial changeset/documentation which prompted for this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is necessary because the getfilectx has changed in a way that makes this change necessary. The change is even documented in a comment in the mercurial sources. In any case, the git-remote-hg test suite reveals the issue.
It would be nice if the commit message is slightly more expanded, by referring the links/text at #27 (comment) for example. I also see that the author uses the S-o-b line, perhaps you should use that too? (implying that you understand the conditions of the S-o-b line of course). |
The commit fixes failures of the test suite with Mercurial 3.2. I don't think there is much else to say. Looking at past commits by the author (and judging on past discussions with him about the subject on the git mailing list), I don't have the feeling he values this much. Anyway, the changes are trivial and obvious. Everybody is free to rewrite them and / or the commit message to their liking. I simply wanted to fix git-remote-hg for my personal use, and thought it might be helpful for others. |
This needs work anyway, as according to Travis, compatibility with hg 3.0 and older has been broken (while it seems to still work with 3.1.2 on my machine). Somebody will have to look into that, too. |
0248802
to
e716a9e
Compare
I'm afraid I'm not in a place to comment on the implementation details but with the current latest from this repo I ended up in a place with this error:
Which is awkwardly unhelpful. And with @fingolfin changes in this pull request, it works. Thanks very much to @fingolfin as I prefer git and this error had me worried that I had to go back to mercurial. Cheers, |
They work, as long as the hg-git / dulwhich versions are suitable. We should eventually verify that.
This needs to be investigated. Failure occurs with hg-git 0.7.0 and various Mercurial versions, including 2.6.3 and 3.2.4).
Note: Please don't be fooled by the failing tests. They are failing for the parent commit, too, and are due to an incompatibility of recent hg dev versions with hg-git 0.7.0. But hg-git dev in turn introduces problems for git-remote-hg of its own, see issue #35. |
This issue is till relevant - not compatible with the latest |
@signalpillar Wait, are you talking about this repos, or are you talking about my fork? |
@fingolfin, I followed instructions from this repo
|
@signalpillar: Can you try the version from fingolfin: |
This is because of unsolved issues with recent mercurial: felipec/git-remote-hg#28
@tboegi, I had the same problem as @signalpillar, using @fingolfin fork fixed it. |
The author of this repository does not come for a long time, all of the latest patches (with this pull request) look in the @fingolfin repository: https://github.com/fingolfin/git-remote-hg |
You can see this commit at e716a9e1 in that new fork. |
Note that if you use Debian or Ubuntu, the |
This fixes issue #27.