Open Stack

On 09/15/2013 10:50 AM, Thomas Goirand wrote:
> Hi,
> 
> There's jsonschema 2.0.0 in Sid, and when I build some of the OpenStack
> packages, I get a huge list of requirement parsing errors:
> 
> 2013-09-12 17:05:55.720 26018 ERROR stevedore.extension [-] Could not
> load 'file': (jsonschema 2.0.0 (/usr/lib/python2.7/dist-packages),
> Requirement.parse('jsonschema>=0.7,<2'))
> 2013-09-12 17:05:55.720 26018 ERROR stevedore.extension [-] (jsonschema
> 2.0.0 (/usr/lib/python2.7/dist-packages),
> Requirement.parse('jsonschema>=0.7,<2'))

This is very weird - that requirement is not one that our file has.

I suggest you add SKIP_PIP_INSTALL=1 to the debian/rules files on all of
the OpenStack things you are packaging - I think it will make things
like that go away - since you are processing depends at the apt side,
there is no need to process them at the python level at runtime too.

> Though, when I have a look at the requirements.txt and
> test-requirements.txt of nova, jsonschema has:
> 
> requirements.txt: jsonschema>=1.3.0,!=1.4.0
> 
> This seems to be fine, so I don't understand what is conflicting. Doing
> a "grep -r jsonschema" on the nova sources gives no result.
> 
> So my questions are:
> - what is creating these parse errors, and how to fix them?
> - could we make it so that OpenStack supports jsonschema 2.0.0, which is
> now in Sid? Where should I look into then?
> - why do we have the above error, while global-requirements.txt doesn't
> ping jsonschema to <2?
> 
> I would very much like to have this resolved, since that's completely
> destroying the unit test results of multiple Debian packages for Havana
> b3, including Nova.
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>