On Thu, Mar 20, 2014 at 10:00 AM, Jeremy Stanley <[email protected]> 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 merged a workaround which should > plaster over the failure on py3k-precise nodes by ripping out the > python3-pip package, but ultimately I don't think it's great for us > to release software requiring a newer pip than is packaged on Ubuntu > 12.04 LTS while we still support that platform. > Looks like we are now in the same boat, I thought we could pin PBR <0.7.0, but something is still not right. Jobs in our setup are still failing because of the pip 1.4 requirement.
We too have chosen to use Ubuntu 12.04 as a supported platform, but now considering bumping pip over the supported version in Ubuntu; we're still on the fence. -- Paul Belanger | PolyBeacon, Inc. Jabber: [email protected] | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
