[IPython-dev] git describe doesn't work?

[Matthias Bussonnier]

Le 24 sept. 2014 à 11:48, Dave Hirschfeld a écrit :

> Matthias Bussonnier <bussonniermatthias <at> gmail.com> writes:
> 
>> 
>> 
>> Le 24 sept. 2014 à 11:06, Dave Hirschfeld a écrit :
>> 
>>> I've observed that git describe doesn't seem to work properly with 
> the 
>>> ipython repo which makes my conda dev builds have the wrong version 
>>> number.
>> 
>> What do you mean by do not work properly ? 
>> The things that you show below seem reasonable.
> 
> As shown, git describe says the tip of master is 1644 commits on from 
> release *2.0.0* which is all well and good, but what you really want to 
> know is how far from the *latest* release you are.
> 
> 
> This is important, because using the output from git describe will 
> result in the latest master (rel-2.0.0-1644-ga2e1c67) comparing less 
> than the last release (rel-2.2.0) which is obviously not what you want.

But the patches that are applied to 2.x and master are different.

2.x cannot really be considered be considers as in between 2.0 and master. 

its like saying that obviously 7.5+0.001im is the middle of 5.0 and 10.0. 

Though I understand what you want to do. 
Would tagging the 2.0.0+1commit to something like 3.0.0-dev suit you ? 

You would still not have 2.1 and 2.2 ancestor of 3.0.0-dev, but it should be simpler for comparison. 

-- 
M

> 
> In [5]: verlib.NormalizedVersion('2.0.0.1644') > 
> verlib.NormalizedVersion('2.2.0')
> Out[5]: False
> 
> It seems James has tracked down the source of the problem, so if it's 
> not intentional that releases aren't ancestors of master it would be 
> nice to ensure they are going forward IMHO
> 
> -Dave
> 
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev