Open Stack

On 01/08/2014 09:26 AM, Noorul Islam Kamal Malmiyoda wrote:
>
> On Jan 8, 2014 6:11 PM, "Sean Dague" <sean at dague.net
> <mailto:sean at dague.net>> wrote:
>  >
>  > On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
>  > > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
>  > > <gokrokvertskhov at mirantis.com
> <mailto:gokrokvertskhov at mirantis.com>> wrote:
>  > >> Should we rather revert patch to make gate working?
>  > >>
>  > >
>  > > I think it is always good to have test packages reside in
>  > > test-requirements.txt. So -1 on reverting that patch.
>  > >
>  > > Here [1] is a temporary solution.
>  > >
>  > > Regards,
>  > > Noorul
>  > >
>  > > [1] https://review.openstack.org/65414
>  >
>  > If Solum is trying to be on the road to being an OpenStack project, why
>  > would it go out of it's way to introduce an incompatibility in the way
>  > all the actual OpenStack packages work in the gate?
>  >
>  > Seems very silly to me, because you'll have to add oslo.sphinx back into
>  > test-requirements.txt the second you want to be considered for
> incubation.
>  >
>
> I am not sure why it seems silly to you. We are not anyhow removing
> oslo.sphinx from the repository. We are just removing it before
> installing the packages from test-requirements.txt in the devstack gate.
> How does that affects incubation? Am I missing something?

So maybe I'm missing something. I don't see how the patch in question or 
the mailing list thread is related to the solum fail. Perhaps being more 
specific about why removing oslo.sphinx from test-requirements.txt is 
the right work around would be good. Because the nature of the fix (hot 
patching requirements) means that by nature something is not working as 
designed.

As far as I can tell this is just an ordering issue. So figure out the 
correct order that things need to happen in.

	-Sean

-- 
Sean Dague
http://dague.net