[meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing

[meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing

[Max Krummenacher]

For native packages the rdepends do not get automatically installed in the recipe
specific sysroot.

Changes in v2:
- Fixed this by adding to DEPENDS of recipes using python-m2crypto-native rather
  than using a new bbclass.

Max Krummenacher (4):
  python-m2crypto: rdepend on python-typing
  crda: add depends on python-typing-native
  pywbem: add depends on python-typing-native
  openlmi-tools: remove blacklist

 meta-networking/recipes-connectivity/crda/crda_3.18.bb        | 4 +---
 meta-oe/recipes-extended/openlmi/openlmi-tools_0.10.5.bb      | 2 --
 meta-oe/recipes-extended/pywbem/pywbem_0.8.0.bb               | 5 +----
 meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb | 3 ++-
 4 files changed, 4 insertions(+), 10 deletions(-)

-- 
2.6.6

[meta-oe][PATCH v2][master-next 1/4] python-m2crypto: rdepend on python-typing

[Max Krummenacher]

python-typing is required at runtime, not at build time.

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
index ca46222..72523bd 100644
--- a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
+++ b/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
@@ -12,7 +12,8 @@ SRC_URI += "file://0001-setup.py-link-in-sysroot-not-in-host-directories.patch "
 PYPI_PACKAGE = "M2Crypto"
 inherit pypi setuptools siteinfo
 
-DEPENDS += "openssl swig-native python-typing"
+DEPENDS += "openssl swig-native"
+RDEPENDS_${PN} += "python-typing"
 
 DISTUTILS_BUILD_ARGS += "build_ext --openssl=${STAGING_DIR_HOST} -I${STAGING_INCDIR}"
 DISTUTILS_INSTALL_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}"
-- 
2.6.6

[meta-oe][PATCH v2][master-next 2/4] crda: add depends on python-typing-native

[Max Krummenacher]

python-m2crypto-native requires python-typing-native.
This fixed the build, remove blacklist.

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 meta-networking/recipes-connectivity/crda/crda_3.18.bb | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/meta-networking/recipes-connectivity/crda/crda_3.18.bb b/meta-networking/recipes-connectivity/crda/crda_3.18.bb
index 2aa9a09..82a297b 100644
--- a/meta-networking/recipes-connectivity/crda/crda_3.18.bb
+++ b/meta-networking/recipes-connectivity/crda/crda_3.18.bb
@@ -4,7 +4,7 @@ SECTION = "net"
 LICENSE = "copyleft-next-0.3.0"
 LIC_FILES_CHKSUM = "file://copyleft-next-0.3.0;md5=8743a2c359037d4d329a31e79eabeffe"
 
-DEPENDS = "python-m2crypto-native python-native libgcrypt libnl openssl"
+DEPENDS = "python-m2crypto-native python-typing-native python-native libgcrypt libnl openssl"
 
 SRC_URI = "https://www.kernel.org/pub/software/network/${BPN}/${BP}.tar.xz \
            file://do-not-run-ldconfig-if-destdir-is-set.patch \
@@ -34,5 +34,3 @@ do_install() {
 }
 
 RDEPENDS_${PN} = "udev wireless-regdb"
-
-PNBLACKLIST[crda] ?= "Fails to build with RSS http://errors.yoctoproject.org/Errors/Details/130675/"
-- 
2.6.6

[meta-oe][PATCH v2][master-next 3/4] pywbem: add depends on python-typing-native

[Max Krummenacher]

python-m2crypto-native requires python-typing-native.
This fixed the build, remove blacklist.

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 meta-oe/recipes-extended/pywbem/pywbem_0.8.0.bb | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/meta-oe/recipes-extended/pywbem/pywbem_0.8.0.bb b/meta-oe/recipes-extended/pywbem/pywbem_0.8.0.bb
index 8b5394e..7f1986e 100644
--- a/meta-oe/recipes-extended/pywbem/pywbem_0.8.0.bb
+++ b/meta-oe/recipes-extended/pywbem/pywbem_0.8.0.bb
@@ -16,7 +16,7 @@ HOMEPAGE = "http://pywbem.sf.net/"
 LICENSE = "LGPLv2"
 LIC_FILES_CHKSUM = "file://pywbem/LICENSE.txt;md5=fbc093901857fcd118f065f900982c24"
 SECTION = "Development/Libraries"
-DEPENDS = "python-m2crypto-native"
+DEPENDS = "python-m2crypto-native python-typing-native"
 SRC_URI = "http://jaist.dl.sourceforge.net/project/${BPN}/${BPN}/${BP}/${BP}-dev.r704.zip"
 SRC_URI[md5sum] = "84072451dcdd1aa9ee82363848faf7ad"
 SRC_URI[sha256sum] = "898035866d3cc741bbcd62c4ac26e633ad07b7c11d89db2472b9f923f3fd3ed8"
@@ -34,6 +34,3 @@ do_install_append() {
 }
 
 BBCLASSEXTEND = "native"
-
-PNBLACKLIST[pywbem] ?= "Fails to build with RSS http://errors.yoctoproject.org/Errors/Details/130596/"
-PNBLACKLIST[pywbem] ?= "Fails to build with RSS http://errors.yoctoproject.org/Errors/Details/130681/"
-- 
2.6.6

[meta-oe][PATCH v2][master-next 4/4] openlmi-tools: remove blacklist

[Max Krummenacher]

Build is fixed for pywbem, pywbem-native.

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 meta-oe/recipes-extended/openlmi/openlmi-tools_0.10.5.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta-oe/recipes-extended/openlmi/openlmi-tools_0.10.5.bb b/meta-oe/recipes-extended/openlmi/openlmi-tools_0.10.5.bb
index cc8e829..b23869d 100644
--- a/meta-oe/recipes-extended/openlmi/openlmi-tools_0.10.5.bb
+++ b/meta-oe/recipes-extended/openlmi/openlmi-tools_0.10.5.bb
@@ -21,5 +21,3 @@ do_compile_prepend() {
 do_install_prepend() {
     cd cli
 }
-
-PNBLACKLIST[openlmi-tools] ?= "Depends on blacklisted pywbem"
-- 
2.6.6

Re: [meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing

[Patrick Ohly]

On Tue, 2017-02-14 at 22:48 +0100, Max Krummenacher wrote:
> For native packages the rdepends do not get automatically installed in the recipe
> specific sysroot.

I'm still not certain whether that RDEPENDS problem is intentional or a
bug which needs to be fixed - see "[OE-core] Does recipe specific
sysrooot (or whatelse in current oe) break native dependencies?"

I don't know how long it might take to resolve this, nor how urgent this
problem is for you, therefore I don't have an opinion whether merging a
(temporary?) workaround is better than waiting.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.

Re: [meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing

[Max Krummenacher]

Hi

2017-02-15 9:07 GMT+01:00 Patrick Ohly <patrick.ohly@intel.com>:
> On Tue, 2017-02-14 at 22:48 +0100, Max Krummenacher wrote:
>> For native packages the rdepends do not get automatically installed in the recipe
>> specific sysroot.
>
> I'm still not certain whether that RDEPENDS problem is intentional or a
> bug which needs to be fixed - see "[OE-core] Does recipe specific
> sysrooot (or whatelse in current oe) break native dependencies?"

IMHO this is a bug.
If I need a tool at compile time I should only have to add that tool to DEPENDS,
this should take care of installing what ever else that tool needs to run.

However I understand Richard's comments that technically this is not easy
to achive so I don't expect a fix soon.

>
> I don't know how long it might take to resolve this, nor how urgent this
> problem is for you, therefore I don't have an opinion whether merging a
> (temporary?) workaround is better than waiting.

I guess that crda is sort of mandatory for images which use WiFi so having
that blacklisted is likely a showstopper for many users.
(pywbem got fixed because grep hinted that it has the identical issue, I don't
even know what it does)

Also the workaround will not hurt once RDEPENDS native are followed, at best
a package is installed in the sysroot because it is listed in two places,
at worst the RDEPENDS is no longer needed but gets still installed because
that change did not propagate to the user of the tool.

So I'm for fixing it with a workaround.

Max

>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel