On Wed, Mar 19, 2014 at 8:52 AM, Monty Taylor <[email protected]> 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. The proposal slave still at apt-installed pip on >>> it. We have an unmerged puppet patch that will take care of this overall >>> - but for now, I applied the manual fix to the slave[1]. I expect it to >>> work now. >> >> >> thanks, Monty for the quick fix! Let's see whether the next jobs work >> fine. >> >> Didn't you want to include the mailing list? > > > Yes. Ooops. Mail fail. > Interesting, I just ran into this for a library I'm trying to build outside OpenStack. My PBR range is setup for pbr>=0.5.21,<1.0 and didn't expect a hard dependency jump for anything less then 1.0. I can see by diff 0.6 and 0.7.0[1] of PBR the pip dependency was bumped, I assume that was unavoidable right?
Would would be the best min / max range for PBR to avoid breakages in the future? For now, I'm going to decrease my version to pbr>=0.5.21,<0.7.0 [1] https://github.com/openstack-dev/pbr/compare/0.6...0.7.0 -- 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
