On Dec 15, 2014, at 2:02 PM, Donald Stufft <don...@stufft.io> wrote:
> >> On Dec 15, 2014, at 1:57 PM, Sean Dague <s...@dague.net> wrote: >> >> On 12/15/2014 01:53 PM, Donald Stufft wrote: >>> >>>> On Dec 15, 2014, at 1:50 PM, Sean Dague <s...@dague.net> wrote: >>>> >>>> On 12/15/2014 12:01 PM, Jeremy Stanley wrote: >>>>> On 2014-12-15 11:53:07 -0500 (-0500), Doug Hellmann wrote: >>>>> [...] >>>>>> This release is primarily meant to update the SQLAlchemy dependency >>>>>> to resolve the issue with the new version of setuptools changing >>>>>> how it evaluates version range specifications. >>>>> [...] >>>>> >>>>> However note that I'm in the middle of forcing a refresh on a couple >>>>> of our PyPI mirror servers, so it may be a couple hours before we >>>>> see the effects of this throughout all of our infrastructure. >>>>> >>>> >>>> It looks like this change has broken the grenade jobs because now >>>> oslo.db 1.3.0 ends up being installed in stable/juno environments, which >>>> has incompatible requirements with the rest of stable juno. >>>> >>>> http://logs.openstack.org/07/137307/1/gate//gate-grenade-dsvm/048ee63//logs/old/screen-s-proxy.txt.gz >>>> >>>> pkg_resources.VersionConflict: SQLAlchemy 0.8.4 is installed but >>>> SQLAlchemy>=0.9.7,<=0.9.99 is required by ['oslo.db'] >>>> >>>> -Sean >>> >>> It should probably use the specifier from Juno which matches the old >>> specifier in functionality. >> >> Probably, but that was specifically reverted here - >> https://review.openstack.org/#/c/138546/2/global-requirements.txt,cm >> > > Not sure I follow, that doesn’t seem to contain any SQLAlchemy changes? > > I mean stable/juno has this -> > SQLAlchemy>=0.8.4,<=0.9.99,!=0.9.0,!=0.9.1,!=0.9.2,!=0.9.3,!=0.9.4,!=0.9.5,!=0.9.6 > and master has this -> SQLAlchemy>=0.9.7,<=0.9.99 > > I forget who it was but someone suggested just dropping 0.8 in global > requirements over the weekend so that’s what I did. > > It appears oslo.db used the SQLAlchemy specifier from master which means that > it won’t work with SQLAlchemy in the 0.8 series. So probably oslo.db should > instead use the one from stable/juno? Master oslo.db has to match the requirements list being used elsewhere in master, so it can’t use the requirements spec from a stable branch. Can we cap oslo.db in juno to 1.2.0? That should work as a minimum version in the requirements list for master, which would let us maintain an overlapping requirements range to support rolling updates. Doug > > --- > Donald Stufft > PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev