On Sat, 2015-08-29 at 19:05 +0000, Jeremy Stanley wrote: > On 2015-08-29 18:44:55 +0200 (+0200), Thomas Bechtold wrote: > > on http://tarballs.openstack.org/python-barbicanclient/ , master > > tarball is not the latest git version. Something seems to be > > broken. > > Any hints how to solve that? > > What makes you say that? The master branch tip as seen at > http://git.openstack.org/cgit/openstack/python-barbicanclient/commit/ > ?h=master > is a5f7531a0f37542be70d0cfbd0fd7f86a38b0539 and the log from the > corresponding run of the python-barbicanclient-branch-tarball job at > http://logs.openstack.org/a5/a5f7531a0f37542be70d0cfbd0fd7f86a38b0539 > /post/python-barbicanclient-branch-tarball/ef9d3c0/console.html.gz > shows checksums matching the tarball I just downloaded from > http://tarballs.openstack.org/python-barbicanclient/python-barbicancl > ient-master.tar.gz > so it seems correct to me at least. Can you elaborate? Interessting. I recognized it because global requirements already has barbicanclient >= 3.3.0 but python-barbicanclient-master.tar.gz is still 3.2.1.dev24 . So I wasn't able to install some packages because of the missing dependency. Maybe the tarball won't be regenerated if only a new git tag is pushed? In that case the latest commit-id doesn't change but the content of the tarball need to change (from 3.2.1.dev24 to 3.3.0). Cheers, Tom