Open Stack

On 2016-01-15 09:09:10 -0600 (-0600), Kyle Mestery wrote:
> OK, after correcting this with the following patch [1], I'm still
> seeing the tarball job generate the wrong tag [2]. The tag should
> now be 2015.1.3, and you can see in git it is in fact changed to
> that [3]. I'm not sure what I've missed here, any pointers
> appreciated!

Doing a git grep for '2015\.1' after checking out that 2015.1.3 tag
turns up that you're also directly shipping a PKG-INFO file there
with the old version hard-coded inside it. I manually tested `tox -e
venv python setup.py sdist` before and after altering the "Version"
line in that file, and have confirmed that has the desired effect. I
guess it's time to update setup.cfg _and_ PKG-INFO to say 2015.1.4
and push one more tag.

Also, a tip to help avoid this in the future... try building an
sdist and bdist_wheel from the tag before you push it, and then
inspect the filenames in the dist directory (maybe even going so
far as to check their contents or install them into a test
virtualenv and make sure you see the right versions). I do this
fairly often if I'm not sure of the state of a particular repo or
branch.
-- 
Jeremy Stanley