linux/meta-virtualization.git/recipes-devtools/python, branch pyro

python-*: use https for pypi URLs

2017-12-02T02:50:56+00:00

Several of the recipes here were using http URLs for source hosted on pypi - pypi apparently no longer supports http so switch to https instead. Apply this commit [1] to pyro branch. [1] https://www.mail-archive.com/meta-virtualization@yoctoproject.org/msg02821.html Signed-off-by: Fabio Berton Signed-off-by: Bruce Ashfield

python-sqlalchemy: uprev to latest in 1.0.x series

2017-01-20T13:58:43+00:00

According to the changelog at (http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html) this is mostly bug fixes. We need a version >= 1.0.10 to properly support the python-oslo.db uprev to stable/newton in meta-cloud-services. NOTE the license checksum has changed do to content change, not because the package license has changed, it is still MIT. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

python-sqlalchemy: Add 1.1.5

2017-01-20T13:58:43+00:00

1) Copy the v1.0.9 bb to create python-sqlalchemy v1.1.5. 2) License checksum changed,since the copyright years were updated. Signed-off-by: Huang Qiyu Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

python-sqlalchemy: 1.0.8 -> 1.0.9

2017-01-17T19:50:33+00:00

Upgrade python-sqlalchemy from 1.0.8 to 1.0.9. Signed-off-by: Huang Qiyu Signed-off-by: Bruce Ashfield

python-sphinx: 1.3.1 -> 1.4.1

2017-01-15T00:26:18+00:00

1) Upgrade python-sphinx from 1.3.1 to 1.4.1 2) License checksum changed,since the copyright years were updated. Signed-off-by: Huang Qiyu Signed-off-by: Bruce Ashfield

python-webob 1.4.1 -> 1.6.0

2017-01-15T00:26:18+00:00

Upgrade python-webob from 1.4.1 to 1.6.0. Signed-off-by: Huang Qiyu Signed-off-by: Bruce Ashfield

openvswitch: fix build host contamination

2017-01-15T00:26:17+00:00

There is only a single PYTHON variable for configure and yet python is used for the build as well as scripts installed on the target. If we set a path in PYTHON as we had we end up using this same path during the build and since it isn't to the sysroot we end up with host contamination (as demonstrated by python failing to import 'six' on build hosts without python-six installed. The best approach is to set PYTHON to "python" when calling configure, ie. without a path. This will use 'python' from the path during build time and by ensuring all the installed scripts use '/usr/bin/env' we can ensure python will be found on the target when the scripts are run. Since 'six' is used as part of the build we have to ensure it is -native'ly buildable and we set all the required build and runtime dependencies. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

python-m2crypto: Fix issue with swig 3.0.5

2016-04-05T15:15:15+00:00

The version 0.22.3 of python-m2crypto fails to work after swig updated to 3.0.5+: AttributeError: 'module' object has no attribute 'PKCS5_SALT_LEN' It's fixed since 0.22.4 and we could update it to latest version, but docker-registry depends on the version 0.22.3, so backport the patch to fix the issue with swig 3.0.5. Signed-off-by: Jackie Huang Signed-off-by: Bruce Ashfield

python-six: uprev to latest

2016-02-09T19:28:41+00:00

The openstack layer requires a version of six >= 1.9.0 Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

bbappend: switch to use a wildcard beyond major version

2015-09-08T13:59:36+00:00

Using a wildcard will simplify things when using meta-virtualization against different yocto or oe branches and prevent having to make future updates to keep in step with package uprevs. The changes found within these bbappend tend to be generic and non-version specific, thus safe for 'porting' via wildcard. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield