Open Stack

Hi infra,

I have been pushing the Swift 2.2.1.rc1 tag this morning in preparation
for Swift 2.2.1 release this week, and it resulted in a
swift-2.2.1c1.tar.gz tarball being generated (instead of the
swift-2.2.1.rc1.tar.gz tarball that my scripts expected).

Tracing back to the logs at:
https://jenkins05.openstack.org/job/swift-tarball/1/consoleFull

it appears that setuptools is warning against using 2.2.1.rc1 as a
version, and then just takes 2.2.1c1 as version instead. So the
"warning" is a bit... definitive:

2014-12-15 09:19:00.162 | venv runtests: commands[0] | python setup.py sdist
2014-12-15 09:19:00.561 |
/home/jenkins/workspace/swift-tarball/.tox/venv/local/lib/python2.7/site-packages/setuptools/dist.py:289:
UserWarning: The version specified requires normalization, consider
using '2.2.1c1' instead of '2.2.1.rc1'.
[...]
2014-12-15 09:19:00.948 | running check
2014-12-15 09:19:00.948 | creating swift-2.2.1c1
2014-12-15 09:19:00.949 | creating swift-2.2.1c1/bin

At this point I have the tag in git and no tarball to upload to
Launchpad and announce. Let me know what I can do (should we remove and
re-tag with something different ? should we fix the -tarball job and
retrigger it manually ?)

Staying put,

-- 
Thierry Carrez (ttx)