Per the original commit this was only included as a temporary measure
until the recipe was available in meta-openembedded. At this point the
meta-openembedded recipe is not only available but has been uprev'd
several times making it more suitable than the recipe we are now
deleting here.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Allow a py2 version of the python-websocket-client package to be
built. This is required to support updates in meta-cloud-services.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fix license path and checksum for python3-dockerpty.
Signed-off-by: Abdur Rehman <abdur_rehman@mentor.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Cleanup the various python-* recipes which download from pypi. The
biggest change is to "inherit pypi" which should result in us always
using current pypi best practices. This will for example ensure we are
using https and not http which is apparently going to be disabled
soon.
Where the default behavior in the pypi class wasn't sufficient we make
use of the PYPI_* variables to overwrite the defaults.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The only user in meta-virtualization is python-bugsnag and there is no
version dependency. This new version is however required by the latest
openstack. Switched to using the "common" pypi.bbclass while we are at
it.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Add python3-docker-pycreds, python3-requests and
python3-websocket-client to RDEPENDS for a functional python docker
module (otherwise even import docker fails).
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This requires some packages as well as the pypi.bbclass from meta-python.
It uses Python 3 as I don't think it makes sense to use Python 2 anymore.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Same version of the recipe is maintained in meta-python, no need to
keep a duplicate here.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Newer version of the recipe (v3.11.1) is already maintained in
meta-python and I couldn't find any hard dependencies on the current
version.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Same recipe is maintained in oe-core, no need to keep a duplicate here.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
There's a newer recipe (v2.13) maintained in meta-python. meta-openstack
explicitly prefers that version over this one, so no point in keeping
this recipe since nobody else is using this version.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This will eventually be available in meta-openembedded so will be able
to be reverted. This will allow us to use openvswitch with python3 in
the interim.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Upgrade python-sqlalchemy from 1.0.8 to 1.0.9.
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Upgrade python-webob from 1.4.1 to 1.6.0.
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <jackie.huang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The openstack layer requires a version of six >= 1.9.0
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The lack of a proper ability to regenerate configure causes the cross
compile detect logic to fail (shown below). It is easiest to just
force the cross compile option at configure time.
| configure: error: in `/opt/buildtmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/python-gevent/1.0.1-r0/gevent-1.0.1/build/temp.linux-x86_64-2.7/libev':
| configure: error: cannot run C compiled programs.
| If you meant to cross compile, use `--host'.
| See `config.log' for more details
| Running '/bin/sh /opt/buildtmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/python-gevent/1.0.1-r0/gevent-1.0.1/libev/configure > configure-output.txt' in /opt/buildtmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/python-gevent/1.0.1-r0/gevent-1.0.1/build/temp.linux-x86_64-2.7/libev
| building 'gevent.core' extension
| creating build/temp.linux-x86_64-2.7/gevent
| ccache arm-wrs-linux-gnueabi-gcc -march=armv7-a -mfloat-abi=hard -mfpu=neon -marm -mthumb-interwork -mtune=cortex-a7 --sysroot=/opt/buildtmp/sysroots/fsl-ls10xx -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -O2 -pipe -g -fPIC -DLIBEV_EMBED=1 -DEV_COMMON= -DEV_CLEANUP_ENABLE=0 -DEV_EMBED_ENABLE=0 -DEV_PERIODIC_ENABLE=0 -Ibuild/temp.linux-x86_64-2.7/libev -Ilibev -I/opt/buildtmp/sysroots/fsl-ls10xx/usr/include/python2.7 -c gevent/gevent.core.c -o build/temp.linux-x86_64-2.7/gevent/gevent.core.o
| In file included from gevent/libev.h:2:0,
| from gevent/gevent.core.c:313:
| libev/ev.c:45:22: fatal error: config.h: No such file or directory
| # include "config.h"
| ^
| compilation terminated.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Work around an issue with python 2.7 not always having SSLv3 available
by allowing v2 or v3 certificates.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
These are a set of dependencies required to build and run docker and
docker-registry which had previously existed in
meta-cloud-services. By moving these from meta-cloud-services to
meta-virtualization we can build and use docker without needing to
include meta-cloud-services. Since meta-cloud-services depends on
meta-virtualization these recipes will still be available for use with
packages/images in meta-cloud-services.
There is a concern that meta-cloud-services contains many python
packages as there exists tight dependency for specific package
versions, this move does not prevent this tight binding from
continuing using various mechanisms made available to layers.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
This is the old 2.7.2 version and it will be found when the
2.7.9 version goes looking for the patch of the same name,
causing do_patch() to fail.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
It is questionable if we need this at all anymore (we probably don't),
but for now, there's no reason to not match the versions.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
redefining THISDIR and using FILESPATH is no longer required in a
"modern" bbappend, and in fact breaks other layers that also patch
python.
Removing THISDIR and using FILESEXTRAPATHS_prepend fixes both issues.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
