There is one in oe-ocore, so remove it, and let python-pbr_4.2.0.bb use the one
in oe-core.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
pyudev uses ctypes to load libudev shared library at runtime which
results in an exception if it cannot be found
Signed-off-by: Florian Wickert <fw@javox-solutions.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The 0.9 branch only supports python>=3.4
License-Update: Use the actual LICENSE file rather than setup.py
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: Change license file from setup.py to
LICENSE, based on the same the same license policy Apache 2.0.
Signed-off-by: Łukasz Gardoń <lukaszgardon555@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This packages license shold be not Apache-2.0 but BSD-2-Clause.
I judgetd by LICENSE file and SPDX file.
Signed-off-by: Takuma Ueba <ueba.takuma@jp.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Since the following commit applied in oe-core
...
21f0c5a distutils/setuptools, distutils3/setuptools3: improve reproducibility
...
It unified var-DISTUTILS_INSTALL_ARGS in distutils and setuptools,
so clean up the duplicated var-DISTUTILS_INSTALL_ARGS in each recipe.
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Remove bundled egg-info from the source tarball as it will be generated
by the build system with the correct permissions during build time.
This fixes a permission denied issue when importing pkg_resources as a
normal user.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This small python module provides a way to manage and compare version
strings which adhere to the Semantic Versioning specification [1].
[1] https://semver.org
Signed-off-by: Dennis Menschel <menschel-d@posteo.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Also the package is licensed under both BSD and LGPL-3.0.
This the license checksum was updated to reflect this.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: Copyright authors changed along with formatting of the license.
License terms remain the same
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update the upstream check regex to restrict to version 1.X.Y
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Based on a recipe from meta-openstack, but with the rmargparse class removed
(which doesn't appear to be needed anymore) and Python 3 support added.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: LICENSE was removed and only PKG-INFO remains in this release. Update the checksum
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: Update the checksum for the latest PKG-INFO release and verify license is still BSD
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: PKG-INFO updated for the latest release and MIT remains the package license
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The distutils class does a 'setup.py clean' now, deleting files which then need
to be regenerated. Add Cython to the build dependencies so this can be done.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The distutils class got a clean via "setup.py clean", but these
recipes doesn't support this yet so disable clean target during
configure
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: Changed back to orginal license from version 0.0.5
Signed-off-by: Alexandru Vasiu <alexandru.vasiu@ni.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The license checksum changes but the license remains the same.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The license checksum changes but the license remains the same.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The license checksum changes but the license remains the same.
The change is only about year, 2017 -> 2018.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The license checksum changes but the license remains the same.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The license checksum changes but the license remains the same.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The license checksum changes but the license remains the same.
The change is just about year, 2013 -> 2018.
Add python3-pytest-runner to DEPENDS to solve the following error.
| distutils.errors.DistutilsError: Could not find suitable distribution \
for Requirement.parse('pytest-runner')
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade python-cryptography from 2.1.4 to 2.2.
here is the change in LICENSE file thats resulting in checksums changes
-from the same in CPython itself, and is licensed under the terms of the PSF
-License Agreement.
+from CPython, and is licensed under the terms of the PSF License Agreement.
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
file /usr/bin/py.test conflicts between attempted installs of python3-pytest-3.4.2-r0 and python-pytest-3.4.2-r0
file /usr/bin/pytest conflicts between attempted installs of python3-pytest-3.4.2-r0 and python-pytest-3.4.2-r0
Signed-off-by: Lei Maohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
It fixes below test failure:
-- snip --
ImportError while importing test module '/usr/lib64/python-cryptography/ptest/tests/test_x509.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/test_x509.py:17: in <module>
import pytz
E ImportError: No module named pytz
-- snip --
Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
"distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr>=1.8')"
Signed-off-by: Lei Maohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add the robotframework serial library which provides the python library
and associated robot keywords to open and communicate with serial devices.
Signed-off-by: Sipke Vriend <sipke.vriend@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add the runtime dependencies robot framework has so they are available on
images including it.
python-robotframework.inc is included by both python3 and python
robot framework.
python3 includes zlib by default so include python-zlib as a runtime
dependency in the python-robotframework recipe and not in the
python3-robotframework.
Signed-off-by: Sipke Vriend <sipke.vriend@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
The module werkzeug.test is moved to the python-werkzeug-tests package
since commit 857ed16. Flask imports werkzeug.tests during exception
handling which results in "ImportError: No module named
'werkzeug.test'".
Signed-off-by: Florian Wickert <fw@javox-solutions.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
ecodes.c is generated file and if we do not specify the
linux input headers it happiliy defaults to /usr/include/
to look for these headers while emitting code for ecodes.c
which can cause gripes when build systems kernel UAPI is
different than the target kernel. Mysterious build errors
or even worse runtime errors can start to appear.
e.g.
| evdev/ecodes.c:603:29: error: 'KEY_ROTATE_LOCK_TOGGLE' undeclared (first use in this function); did you mean 'KEY_ATTENDANT_TOGGLE'?
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Flask-RESTful is a simple framework for creating REST APIs with Flask
Signed-off-by: Andrea Galbusera <gizero@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Pystache is a Python implementation of Mustache. Mustache is a
framework-agnostic, logic-free templating system inspired by ctemplate and et.
Like ctemplate, Mustache "emphasizes separating logic from presentation: it is
impossible to embed application logic in this template language."
Signed-off-by: Christian Poessinger <christian@poessinger.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This module provides the ConfigParser class which implements a basic configuration language which provides a structure similar to what’s found in Microsoft Windows INI files.
Signed-off-by: Alexandru Vasiu <alexandru.vasiu@ni.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Add recipe for python3-websockets v4.0.1. Strictly speaking the package
does not require asyncio but instead builds on top of it and it is
essential for any work.
Make this recipe a native one to allow usage for example in image tests
as a websocket client talking to a device under test.
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
WARNING: python-grpcio-1.8.4-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-setup.py-Do-not-mix-C-and-C-compiler-options.patch
patching file setup.py
Hunk #1 succeeded at 115 with fuzz 2 (offset -1 lines).
Now at patch 0001-setup.py-Do-not-mix-C-and-C-compiler-options.patch
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file configure.ac
Hunk #1 succeeded at 7 with fuzz 2.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file tests/test_import.py
Hunk #4 succeeded at 122 with fuzz 1.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file dbusmock/__init__.py
Hunk #1 succeeded at 14 with fuzz 1.
checking file dbusmock/mockobject.py
Hunk #1 succeeded at 688 (offset 6 lines).
and others
Signed-off-by: Armin Kuster <akuster808@gmail.com>
