search

zestsoftware / zest.releaser

Python software releasing made easy and repeatable
https://zestreleaser.readthedocs.io
GNU General Public License v2.0
201 stars 62 forks source link

Release from Mercurial repos seems to be broken #237

Closed icemac closed 7 years ago

icemac commented 7 years ago

I am using zest.releaser 6.12.3 and mercurial4.3.1.

When using the release command zest.releaser calls hg like this to create the checkout of the current tag: hg clone -r 6.0.5 <source-path> <dest-path> (See https://github.com/zestsoftware/zest.releaser/blob/master/zest/releaser/hg.py#L71-L74)

On my machine this command results in a checkout having revision 6 as parent of the working directory instead if the revision where which belongs to the tag. This was not always the case. I recently updated hg and zest.releaser but I cannot remember which versions I used before.

A solution could be to call clone without -r and later on do a hg update -r <tag> or to use the hash instead of the tag name if it is available.

icemac commented 7 years ago

I was digging deeper into this issue: The problem is not in the zest.releaser code. The hgsubversion extension seems to cause the trouble. Disabling it fixes the issue. See also https://bitbucket.org/durin42/hgsubversion/issues/467/hg-clone-r-broken-when-hgsubversion