Skip to content
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

Using RMT with Mercurial and Simple version generation is broken when Mercurial version > 3 #77

Open
krtek4 opened this issue Aug 7, 2014 · 4 comments · May be fixed by #102
Open

Using RMT with Mercurial and Simple version generation is broken when Mercurial version > 3 #77

krtek4 opened this issue Aug 7, 2014 · 4 comments · May be fixed by #102
Labels

Comments

@krtek4
Copy link
Contributor

krtek4 commented Aug 7, 2014

It seems that beginning with Mercurial version 3.0, it is now impossible to use purely numeric tag name :

$ hg tag 1
abort: cannot use an integer as a name
$ hg --version
Mercurial Distributed SCM (version 3.1)

But it is working on version 2.2 :

$ hg tag 1
$ hg --version
Mercurial Distributed SCM (version 2.2.2)

I don't know if there is a lot of Mercurial users out there using RMT, but this issue should be addressed. I see two possible solutions :

  1. Forbid the use the Simple version generation when Mercurial is used
  2. Add some kind of prefix to simple tags, like 'v\d+' instead of the current '\d+'

The problem with 2) is that it is can be a big BC break depending on the implementation.

FYI : the test suite is currently failing when ran with the "faulty" Mercurial version.

@krtek4 krtek4 changed the title Using RMT with Mercurial and Simple tag generation is broken. Using RMT with Mercurial and Simple tag generation is broken when Mercurial version > 3 Aug 7, 2014
@krtek4 krtek4 changed the title Using RMT with Mercurial and Simple tag generation is broken when Mercurial version > 3 Using RMT with Mercurial and Simple version generation is broken when Mercurial version > 3 Aug 7, 2014
@krtek4 krtek4 added the bug label Aug 7, 2014
@jeanmonod
Copy link
Member

Hi @krtek4,
Thanks for this detailed bug report. Personally I will go for solution 2) but without doing it automatically. What about:

  1. Adding a warning about that issue in the documentation, recommending to use the existing RMT prefix mechanism.
  2. Better catching the exception, and forwarding the user to the documentation

So like this the BC break stay in the mercurial side. What do you think of this approach?

@jeanmonod
Copy link
Member

@krtek4 up!

@krtek4
Copy link
Contributor Author

krtek4 commented May 7, 2015

Stop resurrecting old bugs, it's not Zombie Jesus Day !

Problem is, the solution you propose does not really fix the tests... I'll try to have a look :)

@jeanmonod
Copy link
Member

Was not able to release yesterday ;) I have Mercurial 3.2 on my Mac and no easy way to downgrade...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants