On 5 January 2016 at 12:01, Robert Collins <robertc at robertcollins.net> wrote: > On 5 January 2016 at 11:59, Robert Collins <robertc at robertcollins.net> wrote: >> This is odd indeed. pbr is not meant to have a dep on testrepository, >> and you can see in >> https://git.openstack.org/cgit/openstack-dev/pbr/tree/pbr/testr_command.py#n150 >> that we only access it if it is installed.... and we use latest pbr >> everywhere because otherwise we can't deal with ecosystem changes to >> e.g. setuptools or pip. >> >> http://logs.openstack.org/96/262296/2/check/gate-tempest-dsvm-full/e47e5c6/logs/devstacklog.txt.gz#_2015-12-30_09_53_14_200 >> shows that the latest pbr (1.8.1 which would work) is being >> downgraded. Thats when the problem is introduced. However, kilo has >> that special thing where pbr is capped because a lot of dependencies >> error due to version disagreements (not API breaks - pbr is >> compatible!), so this is expected :(. >> >> I'm not sure what has caused testrepository to not be installed in >> this scenario, but thats what I'd be looking at. >> > > Further to that, I suspect setuptools may have changed - > https://pypi.python.org/pypi/setuptools - 19.2 was released > suspiciously close to the point errors were reported (25th dec). > > Looking now.. Indeed - https://bitbucket.org/pypa/setuptools/commits/fb35fcade302fa828d34e6aff952ec2398f2c877?at=get_command_list - the failing bit AFAICT is indeed new code :/. -Rob -- Robert Collins <rbtcollins at hpe.com> Distinguished Technologist HP Converged Cloud