On Thu, Mar 20, 2014 at 10:00 AM, Jeremy Stanley wrote:
> This is also biting us on Python 3.3 jobs, because for some reason
> tox is using the system-installed python3-pip v1.3.1 when building
> the virtualenv and subsequently hitting a version mismatch with
> pbr's >=1.4 requirement. We've just
This is also biting us on Python 3.3 jobs, because for some reason
tox is using the system-installed python3-pip v1.3.1 when building
the virtualenv and subsequently hitting a version mismatch with
pbr's >=1.4 requirement. We've just merged a workaround which should
plaster over the failure on py3k
On Wed, Mar 19, 2014 at 8:52 AM, Monty Taylor wrote:
> On 03/19/2014 07:01 AM, Andreas Jaeger wrote:
>>
>> On 03/19/2014 10:40 AM, Monty Taylor wrote:
>>>
>>> On 03/19/2014 05:07 AM, Monty Taylor wrote:
Yes. I think we should revert the pbr >= 1.4 patch.
>>>
>>>
>>> Ok - I looked further
On 03/19/2014 07:01 AM, Andreas Jaeger wrote:
On 03/19/2014 10:40 AM, Monty Taylor wrote:
On 03/19/2014 05:07 AM, Monty Taylor wrote:
Yes. I think we should revert the pbr >= 1.4 patch.
Ok - I looked further. The proposal slave still at apt-installed pip on
it. We have an unmerged puppet patc
Yes. I think we should revert the pbr >= 1.4 patch.
On Mar 19, 2014 11:57 AM, Andreas Jaeger wrote:
>
> I see many propose-translation-jobs failing today that worked yesterday, for
> example:
> https://jenkins.openstack.org/job/cinder-propose-translation-update/lastBuild/console
>
> https://j
I see many propose-translation-jobs failing today that worked yesterday, for
example:
https://jenkins.openstack.org/job/cinder-propose-translation-update/lastBuild/console
https://jenkins.openstack.org/job/ceilometer-propose-translation-update/lastBuild/console
Log file shows:
2014-03-19 06:02:10
