Reverted the neutron change that started using this, which is the quickest path to unbreaking the children. We’ll have to unwind those child projects first.
doug > On Apr 24, 2016, at 8:09 AM, Gary Kotton <gkot...@vmware.com> wrote: > > Another example is Lbaas - https://review.openstack.org/#/c/309766 > <https://review.openstack.org/#/c/309766>/ > > I have posted https://review.openstack.org/309770 > <https://review.openstack.org/309770> > > Its either that or we skip the current neutron-lib in the requirements file. > > Neutron lib cores please look ASAP as the whole community is kind of stuck at > the moment… > > From: Gary Kotton <gkot...@vmware.com <mailto:gkot...@vmware.com>> > Reply-To: OpenStack List <openstack-dev@lists.openstack.org > <mailto:openstack-dev@lists.openstack.org>> > Date: Sunday, April 24, 2016 at 4:48 PM > To: OpenStack List <openstack-dev@lists.openstack.org > <mailto:openstack-dev@lists.openstack.org>> > Subject: [openstack-dev] [Neutron] Neutron lib hack has broken all decomposed > projects > > Hi, > Commit 4b17f1da1a5f65f0c4db395034ed732174a19315 has broken the pep8 of all of > the decomposed projects. > Do we need this hacking check? Can we have it reverted > An example of this is - > OVN - > http://logs.openstack.org/35/299835/3/check/gate-networking-ovn-pep8/3ad066e/console.html > > <http://logs.openstack.org/35/299835/3/check/gate-networking-ovn-pep8/3ad066e/console.html> > Thanks > Gary > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
