[yocto] The basehash value changed from...

2017-09-07 Thread Zoran Stojsavljevic 
While re-compiling the whole YOCTO load for freescale i.MX6, where I have
added Qt5 layers (and it failed many times, so I needed to do some tricks
there), I encounter the following warning (in *ORANGE*) and error (in *RED*)
while finishing the build:

*WARNING: Duplicate inclusion for
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-bsp-common/conf/tdx_version.conf
in
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/tdx-image-fstype.inc*
*ERROR: When reparsing
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/angstrom-lxde-image.bb.do_image_teziimg,
the basehash value changed from b7b4f312b8b657bfdd068ebd8e2dd104 to
1e71714a9c01964cdc724c52290abee4. The metadata is not deterministic and
this needs to be fixed.*
NOTE: Tasks Summary: Attempted 7415 tasks of which 7394 didn't need to be
rerun and all succeeded.
NOTE: Writing buildhistory

It built (after all) complete deploy with all the images. I kind of get
what is going on here.

Question: how to rebuild the complete deploy/images NOT deleting tmp/? It
compiled overall (in two steps) > 10h. Do I need to touch some file?

Thank you,
Zoran
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] The basehash value changed from...

2017-09-07 Thread Khem Raj 
On Thu, Sep 7, 2017 at 12:37 AM, Zoran Stojsavljevic
 wrote:
> While re-compiling the whole YOCTO load for freescale i.MX6, where I have
> added Qt5 layers (and it failed many times, so I needed to do some tricks
> there), I encounter the following warning (in ORANGE) and error (in RED)
> while finishing the build:
>
> WARNING: Duplicate inclusion for
> /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-bsp-common/conf/tdx_version.conf
> in
> /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/tdx-image-fstype.inc
> ERROR: When reparsing
> /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/angstrom-lxde-image.bb.do_image_teziimg,
> the basehash value changed from b7b4f312b8b657bfdd068ebd8e2dd104 to
> 1e71714a9c01964cdc724c52290abee4. The metadata is not deterministic and this
> needs to be fixed.
> NOTE: Tasks Summary: Attempted 7415 tasks of which 7394 didn't need to be
> rerun and all succeeded.
> NOTE: Writing buildhistory
>
> It built (after all) complete deploy with all the images. I kind of get what
> is going on here.
>
> Question: how to rebuild the complete deploy/images NOT deleting tmp/? It
> compiled overall (in two steps) > 10h. Do I need to touch some file?
>

if you keep your sstate-cache directory then delete tmp/ dir is what you need
to do. Rebuilding from sstate-cache is very quick

> Thank you,
> Zoran
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] cannot re-use shared state cache between build hosts

2017-09-07 Thread Andrea Galbusera 
On Mon, Sep 4, 2017 at 10:56 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:

> On Monday, 4 September 2017 7:59:55 PM NZST Andrea Galbusera wrote:
> > On Mon, Sep 4, 2017 at 9:33 AM, Patrick Ohly 
> wrote:
> > > More recent bitbake should not fail like that anymore. It's still
> > > better to use an HTTP server that performs better, though.
> > >
> > > commit 6fa07752bbd3ac345cd8617da49a70e0b2dd565f
> > > Author: Patrick Ohly 
> > > Date:   Mon Jul 17 15:25:10 2017 +0200
> > >
> > > fetch2/wget.py: improve error handling during sstate check
> > >
> > > When the sstate is accessed via HTTP, the existence check can fail
> due
> > > to network issues, in which case bitbake silently continues without
> > > sstate.
> > >
> > > One such network issue is an HTTP server like Python's own
> SimpleHTTP
> > > which closes the TCP connection despite an explicit "Keep-Alive" in
> > > the HTTP request header. The server does that without a "close" in
> the
> > > HTTP response header, so the socket remains in the connection
> cache,
> > > leading to "urlopen failed:  > > descriptor>" (only visible in "bitbake -D -D" output) when trying
> to
> > > use the cached connection again.
> > >
> > > The connection might also get closed for other reasons (proxy,
> > > timeouts, etc.), so this is something that the client should be
> able
> > > to handle.
> > >
> > > This is achieved by checking for the error, removing the bad
> > > connection, and letting the check_status() method try again with a
> new
> > > connection. It is necessary to let the second attempt fail
> > > permanently, because bad proxy setups have been observed to also
> lead
> > > to such broken connections. In that case, we need to abort for real
> > > after trying twice, otherwise a build would just hang forever.
> > >
> > > [YOCTO #11782]
> > >
> >
> > Thank you Patrick for pointing that out. While debugging the issue on
> morty
> > I had some reminiscence of seeing your patch on the list, but I wasn't
> able
> > to find it back in morty's history hence inferring it landed later on.
> > Anyway doing this test on morty was a requirement... Thanks again for
> your
> > clarification. Would such a patch be suitable for eventually being
> > back-ported to morty?
>
> Doesn't look too invasive to me at least, so I'd support it.
>

I did some positive tests with Patrick's patch on top of morty and it
improves a lot the situation even with SimpleHTTPServer. Than I'd like to
propose it is backported to morty and, after further testing, reasonably
should land in pyro too. But I'm unsure how such a request should be
submitted. Since it affects bitbake, what's the proper way and which list
should I send such a request?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] The basehash value changed from...

2017-09-07 Thread Zoran Stojsavljevic 
> If you keep your sstate-cache directory then delete tmp/ dir is what you
need
> to do. Rebuilding from sstate-cache is very quick.

It does not help. Since I'll have at the end/I'll end-up with the same
problem. My best guess. :-(

Since I am building the whole humongous YOCTO build not in one, rather in
two steps, like this:

bitbake meta-toolchain-qt5 (5 hours build on my HP EliteBook 840 G1)
bitbake angstrom-lxde-image (5 hours build on my HP EliteBook 840 G1)

Here, my best guess is that the first build sets its own hash, which
the second sets also its own (very
different), then makes hash checks in deploy/ tree, and fails... !?

Thank you, Zoran


On Thu, Sep 7, 2017 at 9:42 AM, Khem Raj  wrote:

> On Thu, Sep 7, 2017 at 12:37 AM, Zoran Stojsavljevic
>  wrote:
> > While re-compiling the whole YOCTO load for freescale i.MX6, where I have
> > added Qt5 layers (and it failed many times, so I needed to do some tricks
> > there), I encounter the following warning (in ORANGE) and error (in RED)
> > while finishing the build:
> >
> > WARNING: Duplicate inclusion for
> > /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/
> meta-toradex-bsp-common/conf/tdx_version.conf
> > in
> > /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/
> meta-toradex-demos/recipes-images/images/tdx-image-fstype.inc
> > ERROR: When reparsing
> > /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/
> meta-toradex-demos/recipes-images/images/angstrom-lxde-
> image.bb.do_image_teziimg,
> > the basehash value changed from b7b4f312b8b657bfdd068ebd8e2dd104 to
> > 1e71714a9c01964cdc724c52290abee4. The metadata is not deterministic and
> this
> > needs to be fixed.
> > NOTE: Tasks Summary: Attempted 7415 tasks of which 7394 didn't need to be
> > rerun and all succeeded.
> > NOTE: Writing buildhistory
> >
> > It built (after all) complete deploy with all the images. I kind of get
> what
> > is going on here.
> >
> > Question: how to rebuild the complete deploy/images NOT deleting tmp/? It
> > compiled overall (in two steps) > 10h. Do I need to touch some file?
> >
>
> if you keep your sstate-cache directory then delete tmp/ dir is what you
> need
> to do. Rebuilding from sstate-cache is very quick
>
> > Thank you,
> > Zoran
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] The basehash value changed from...

2017-09-07 Thread Mike Looijmans 

On 07-09-17 11:06, Zoran Stojsavljevic wrote:

 > If you keep your sstate-cache directory then delete tmp/ dir is what you need
 > to do. Rebuilding from sstate-cache is very quick.

It does not help. Since I'll have at the end/I'll end-up with the same 
problem. My best guess. :-(


Since I am building the whole humongous YOCTO build not in one, rather in two 
steps, like this:


|bitbake meta-toolchain-qt5 (5 hours build||on my HP EliteBook 840 G1)
||bitbake angstrom-lxde-image|  (5 hours build on my HP EliteBook 840 G1)

Here, my best guess is that the first build sets its own hash, which the 
second sets also its own (very

different), then makes hash checks in deploy/ tree, and fails... !?


You should be able to do "bitbake meta-toolchain-qt5 angstrom-lxde-image" in 
one go. That should be faster than two separate runs.


If you change the DISTRO, you'll invalidate your "tmp" building dir resulting 
in loads of new stuff being built.


If you need two distros, make two build enviroments from them. You should 
share the sstate-cache directory between them (saves tons on building 
compilers and such) but not the "tmp" directory.




On Thu, Sep 7, 2017 at 9:42 AM, Khem Raj > wrote:


On Thu, Sep 7, 2017 at 12:37 AM, Zoran Stojsavljevic
mailto:zoran.stojsavlje...@gmail.com>> 
wrote:
> While re-compiling the whole YOCTO load for freescale i.MX6, where I have
> added Qt5 layers (and it failed many times, so I needed to do some tricks
> there), I encounter the following warning (in ORANGE) and error (in RED)
> while finishing the build:
>
> WARNING: Duplicate inclusion for
> 
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-bsp-common/conf/tdx_version.conf
> in
> 
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/tdx-image-fstype.inc
> ERROR: When reparsing
> 
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/angstrom-lxde-image.bb.do_image_teziimg,
> the basehash value changed from b7b4f312b8b657bfdd068ebd8e2dd104 to
> 1e71714a9c01964cdc724c52290abee4. The metadata is not deterministic and 
this
> needs to be fixed.
> NOTE: Tasks Summary: Attempted 7415 tasks of which 7394 didn't need to be
> rerun and all succeeded.
> NOTE: Writing buildhistory
>
> It built (after all) complete deploy with all the images. I kind of get 
what
> is going on here.
>
> Question: how to rebuild the complete deploy/images NOT deleting tmp/? It
> compiled overall (in two steps) > 10h. Do I need to touch some file?
>

if you keep your sstate-cache directory then delete tmp/ dir is what you 
need
to do. Rebuilding from sstate-cache is very quick

 > Thank you,
 > Zoran
 >
>
> --
> 


Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail



___

> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto

>






--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/5] rpi-gpio: Update to 0.6.3

2017-09-07 Thread Andrei Gherzan 
As well integrate with meta-oe bbclass pypi.

Signed-off-by: Andrei Gherzan 
---
 recipes-devtools/python/rpi-gpio_0.6.2.bb | 21 -
 recipes-devtools/python/rpi-gpio_0.6.3.bb | 14 ++
 2 files changed, 14 insertions(+), 21 deletions(-)
 delete mode 100644 recipes-devtools/python/rpi-gpio_0.6.2.bb
 create mode 100644 recipes-devtools/python/rpi-gpio_0.6.3.bb

diff --git a/recipes-devtools/python/rpi-gpio_0.6.2.bb 
b/recipes-devtools/python/rpi-gpio_0.6.2.bb
deleted file mode 100644
index 9c72168..000
--- a/recipes-devtools/python/rpi-gpio_0.6.2.bb
+++ /dev/null
@@ -1,21 +0,0 @@
-DESCRIPTION = "A module to control Raspberry Pi GPIO channels"
-HOMEPAGE = "http://code.google.com/p/raspberry-gpio-python/";
-SECTION = "devel/python"
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=9b95630a648966b142f1a0dcea001cb7"
-
-SRCNAME = "RPi.GPIO"
-
-SRC_URI = "\
-  
http://pypi.python.org/packages/source/R/RPi.GPIO/${SRCNAME}-${PV}.tar.gz \
-  file://0001-Remove-nested-functions.patch \
-  "
-SRC_URI[md5sum] = "9db86fd5f3bae872de9dbb068ee0b096"
-SRC_URI[sha256sum] = 
"82acff0ef6bbe3cdf6f4dbdd73d96add5294bb94baf7f51c1d901861af3c2392"
-
-S = "${WORKDIR}/${SRCNAME}-${PV}"
-
-inherit distutils
-
-COMPATIBLE_MACHINE = "^rpi$"
-
diff --git a/recipes-devtools/python/rpi-gpio_0.6.3.bb 
b/recipes-devtools/python/rpi-gpio_0.6.3.bb
new file mode 100644
index 000..d0ff00a
--- /dev/null
+++ b/recipes-devtools/python/rpi-gpio_0.6.3.bb
@@ -0,0 +1,14 @@
+DESCRIPTION = "A module to control Raspberry Pi GPIO channels"
+HOMEPAGE = "http://code.google.com/p/raspberry-gpio-python/";
+SECTION = "devel/python"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=9b95630a648966b142f1a0dcea001cb7"
+
+PYPI_PACKAGE = "RPi.GPIO"
+inherit pypi distutils
+
+SRC_URI += "file://0001-Remove-nested-functions.patch"
+SRC_URI[md5sum] = "e4abe1cfb5eacebe53078032256eb837"
+SRC_URI[sha256sum] = 
"a5fc0eb5e401963b6c0a03650da6b42c4005f02d962b81241d96c98d0a578516"
+
+COMPATIBLE_MACHINE = "^rpi$"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/5] python-sense-hat: Update to 2.2.0

2017-09-07 Thread Andrei Gherzan 
As well integrate with meta-oe bbclass pypi.

Signed-off-by: Andrei Gherzan 
---
 recipes-devtools/python/python-sense-hat_2.1.0.bb | 28 ---
 recipes-devtools/python/python-sense-hat_2.2.0.bb | 24 +++
 2 files changed, 24 insertions(+), 28 deletions(-)
 delete mode 100644 recipes-devtools/python/python-sense-hat_2.1.0.bb
 create mode 100644 recipes-devtools/python/python-sense-hat_2.2.0.bb

diff --git a/recipes-devtools/python/python-sense-hat_2.1.0.bb 
b/recipes-devtools/python/python-sense-hat_2.1.0.bb
deleted file mode 100644
index e990a28..000
--- a/recipes-devtools/python/python-sense-hat_2.1.0.bb
+++ /dev/null
@@ -1,28 +0,0 @@
-SUMMARY = "Python module to control the Raspberry Pi Sense HAT used in the 
Astro Pi mission"
-HOMEPAGE = "https://github.com/RPi-Distro/python-sense-hat";
-SECTION = "devel/python"
-LICENSE = "BSD"
-LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=d80fe312e1ff5fbd97369b093bf21cda"
-
-SRCNAME = "sense-hat"
-
-SRC_URI = 
"https://pypi.python.org/packages/source/s/${SRCNAME}/${SRCNAME}-${PV}.tar.gz";
-
-SRC_URI[md5sum] = "71217f15ea963040f06e2f50722186ca"
-SRC_URI[sha256sum] = 
"c6c76707c0ea514e4b0f1f96f1b5b79755875891aae037df7434b6aad7b9dbca"
-
-S = "${WORKDIR}/${SRCNAME}-${PV}"
-
-inherit setuptools
-
-DEPENDS += " \
-jpeg \
-zlib \
-freetype \
-"
-
-RDEPENDS_${PN} += " \
-python-numpy \
-python-rtimu \
-python-imaging \
-"
diff --git a/recipes-devtools/python/python-sense-hat_2.2.0.bb 
b/recipes-devtools/python/python-sense-hat_2.2.0.bb
new file mode 100644
index 000..f7c4e34
--- /dev/null
+++ b/recipes-devtools/python/python-sense-hat_2.2.0.bb
@@ -0,0 +1,24 @@
+SUMMARY = "Python module to control the Raspberry Pi Sense HAT used in the 
Astro Pi mission"
+HOMEPAGE = "https://github.com/RPi-Distro/python-sense-hat";
+SECTION = "devel/python"
+LICENSE = "BSD"
+LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=d80fe312e1ff5fbd97369b093bf21cda"
+
+inherit setuptools pypi
+
+PYPI_PACKAGE = "sense-hat"
+
+SRC_URI[md5sum] = "69929250cb72349a8a82edf2584b1d83"
+SRC_URI[sha256sum] = 
"f000998d042d96ed722d459312e1bebd0107f9f3015cd34b3e4fabcab9c800af"
+
+DEPENDS += " \
+jpeg \
+zlib \
+freetype \
+"
+
+RDEPENDS_${PN} += " \
+python-numpy \
+python-rtimu \
+python-imaging \
+"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 3/5] pi-blaster: Update to current master HEAD

2017-09-07 Thread Andrei Gherzan 
License in the README was moved a couple of lines below.

Signed-off-by: Andrei Gherzan 
---
 recipes-devtools/pi-blaster/pi-blaster.inc| 2 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc 
b/recipes-devtools/pi-blaster/pi-blaster.inc
index 6ea4fa3..3cb79cc 100644
--- a/recipes-devtools/pi-blaster/pi-blaster.inc
+++ b/recipes-devtools/pi-blaster/pi-blaster.inc
@@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins you 
request of a Raspbe
 HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
 SECTION = "devel/libs"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
+LIC_FILES_CHKSUM = 
"file://README.md;beginline=225;endline=252;md5=a012868ef5f83b9f257af253d7cb07a3"
 
 SRC_URI = "git://github.com/sarfata/pi-blaster \
file://remove-initscript-lsb-dependency.patch \
diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb 
b/recipes-devtools/pi-blaster/pi-blaster_git.bb
index ac812ab..730f9d3 100644
--- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
+++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
@@ -1,3 +1,3 @@
 require pi-blaster.inc
 
-SRCREV = "9f45eb23a8a3b2d1c08d08a6d68f206fe91ecf4c"
+SRCREV = "1035ad7dffb270c40eec1bb3a654171a755fba98"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 4/5] omxplayer: Update to current master HEAD

2017-09-07 Thread Andrei Gherzan 
Signed-off-by: Andrei Gherzan 
---
 recipes-multimedia/omxplayer/omxplayer_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index 0e0f9ba..713dacf 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
 DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh 
libomxil coreutils-native curl-native"
 PR = "r4"
 
-SRCREV = "061425a5eabf6e9ee43229911c073a863d144038"
+SRCREV = "b8ff59dccd9307f10dad71bec2525a95bd6c603b"
 SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
file://0001-Remove-Makefile.include-which-includes-hardcoded.patch \

file://0002-Libraries-and-headers-from-ffmpeg-are-installed-in-u.patch \
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 5/5] userland: Update to current master HEAD

2017-09-07 Thread Andrei Gherzan 
Signed-off-by: Andrei Gherzan 
---
 recipes-graphics/userland/userland_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index 8ff1411..1fc0717 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -16,7 +16,7 @@ COMPATIBLE_MACHINE = "^rpi$"
 
 SRCBRANCH = "master"
 SRCFORK = "raspberrypi"
-SRCREV = "50d3cb5f4ee95a9513bb9f94d661947e9e6ac085"
+SRCREV = "3caf0cd4a61f46b71eff49422c36e1cd2727ab45"
 
 SRC_URI = "\
 git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 1/5] rpi-gpio: Update to 0.6.3

2017-09-07 Thread Andrei Gherzan 
On Thu, Sep 7, 2017 at 2:24 PM, Andrei Gherzan  wrote:

> As well integrate with meta-oe bbclass pypi.
>
> Signed-off-by: Andrei Gherzan 
> ---
>  recipes-devtools/python/rpi-gpio_0.6.2.bb | 21 -
>  recipes-devtools/python/rpi-gpio_0.6.3.bb | 14 ++
>  2 files changed, 14 insertions(+), 21 deletions(-)
>  delete mode 100644 recipes-devtools/python/rpi-gpio_0.6.2.bb
>  create mode 100644 recipes-devtools/python/rpi-gpio_0.6.3.bb
>
> diff --git a/recipes-devtools/python/rpi-gpio_0.6.2.bb
> b/recipes-devtools/python/rpi-gpio_0.6.2.bb
> deleted file mode 100644
> index 9c72168..000
> --- a/recipes-devtools/python/rpi-gpio_0.6.2.bb
> +++ /dev/null
> @@ -1,21 +0,0 @@
> -DESCRIPTION = "A module to control Raspberry Pi GPIO channels"
> -HOMEPAGE = "http://code.google.com/p/raspberry-gpio-python/";
> -SECTION = "devel/python"
> -LICENSE = "MIT"
> -LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=9b95630a648966b142f1a0dcea001c
> b7"
> -
> -SRCNAME = "RPi.GPIO"
> -
> -SRC_URI = "\
> -  http://pypi.python.org/packages/source/R/RPi.GPIO/${
> SRCNAME}-${PV}.tar.gz \
> -  file://0001-Remove-nested-functions.patch \
> -  "
> -SRC_URI[md5sum] = "9db86fd5f3bae872de9dbb068ee0b096"
> -SRC_URI[sha256sum] = "82acff0ef6bbe3cdf6f4dbdd73d96a
> dd5294bb94baf7f51c1d901861af3c2392"
> -
> -S = "${WORKDIR}/${SRCNAME}-${PV}"
> -
> -inherit distutils
> -
> -COMPATIBLE_MACHINE = "^rpi$"
> -
> diff --git a/recipes-devtools/python/rpi-gpio_0.6.3.bb
> b/recipes-devtools/python/rpi-gpio_0.6.3.bb
> new file mode 100644
> index 000..d0ff00a
> --- /dev/null
> +++ b/recipes-devtools/python/rpi-gpio_0.6.3.bb
> @@ -0,0 +1,14 @@
> +DESCRIPTION = "A module to control Raspberry Pi GPIO channels"
> +HOMEPAGE = "http://code.google.com/p/raspberry-gpio-python/";
> +SECTION = "devel/python"
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=9b95630a648966b142f1a0dcea001c
> b7"
> +
> +PYPI_PACKAGE = "RPi.GPIO"
> +inherit pypi distutils
> +
> +SRC_URI += "file://0001-Remove-nested-functions.patch"
> +SRC_URI[md5sum] = "e4abe1cfb5eacebe53078032256eb837"
> +SRC_URI[sha256sum] = "a5fc0eb5e401963b6c0a03650da6b4
> 2c4005f02d962b81241d96c98d0a578516"
> +
> +COMPATIBLE_MACHINE = "^rpi$"
> --
> 2.7.4
>

Please forgive the missing tag. I will not resend to avoid more emails.
I'll add it if a new version is needed.

Sorry once again,
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Pyro's uninative and libstdc++ symbols

2017-09-07 Thread Raphael Kubo da Costa 
Richard Purdie  writes:

> On Fri, 2017-09-01 at 12:14 -0700, akuster wrote:
>> On 08/29/2017 01:03 AM, Richard Purdie wrote:
>> >
>> > On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote:
>> > >
>> > > I've recently updated my host system to Fedora 26, which has GCC
>> > > 7.
>> > >
>> > > This seems to be causing some issues on Pyro, where I have a
>> > > -native
>> > > recipe that is built with my system's g++ and ends up generating
>> > > a
>> > > binary with the following symbol:
>> > >
>> > >    DF
>> > > *UND*    GLIBCXX_3.4.23
>> > > std::basic_string,
>> > > std::allocator
>> > > >
>> > > > ::basic_string(std::string const&, unsigned long,
>> > > std::allocator const&)
>> > >
>> > > GLIBCXX_3.4.23 is not part of Pyro's uninative's libstdc++, so
>> > > when
>> > > that
>> > > binary is invoked in another (non-native) recipe as part of
>> > > do_configure
>> > > it fails to run:
>> > >
>> > >  gn: /data/src/yocto/poky/build/tmp/sysroots-
>> > > uninative/x86_64-
>> > > linux/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.23' not found
>> > > (required by gn)
>> > >
>> > > Is there anything I should be doing differently here?
>> > We need to update the uninative version in pyro to the more recent
>> is this action just a straight forward backport from Master?
>
> Yes, should be...

For the record, I think Richard fixed this with pyro commit
98dcaa9d2c95328eedd6d3608f41c808509348b4 ("uninative: Update to 1.7
uninative release"). I can confirm I can continue using all the
uninative bits on Fedora 26 now. Thanks!
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] tpm2.0-tss: fix systemd package list

2017-09-07 Thread Patrick Ohly 
Commit 4c4fa8c "tpm2.0-tss: install resourcemgr service" introduced
systemd support for the resourcemgr package, but left the default
${PN} in SYSTEMD_PACKAGES, leading to an apparently harmless (?) build
error, emitted by systemd.bbclass via bb.error() because tpm2.0-tss
does not have a package of that name:

ERROR: tpm2.0-tss-git-r0 do_package: tpm2.0-tss does not appear in package 
list, please add it

Signed-off-by: Patrick Ohly 
---
 meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb 
b/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb
index 14ec0ab..fd5ace8 100644
--- a/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb
+++ b/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb
@@ -33,7 +33,7 @@ EXTRA_USERS_PARAMS = "\
groupadd tss; \
"
 
-SYSTEMD_PACKAGES += "resourcemgr"
+SYSTEMD_PACKAGES = "resourcemgr"
 SYSTEMD_SERVICE_resourcemgr = "resourcemgr.service"
 SYSTEMD_AUTO_ENABLE_resourcemgr = "enable"
 

base-commit: 1014cc61fc1d5723f77fcd1a0147f3ca10519171
-- 
git-series 0.9.1
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Working behind a Palo Alto firewall/proxy

2017-09-07 Thread Greg Wilson-Lindberg 
Hi Andre,


Here is the complete error output:

ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher 
failure: Fetch command export 
DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-9ReQWXYEk1"; export 
SSH_AUTH_SOCK="/run/user/1000/keyring-4PGABB/ssh"; export 
PATH="/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/raspberrypi3/usr/bin/crossscripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/bitbake/bin:/home/gwilson/TEE:/home/gwilson/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/microchip/xc32/v1.34/bin:/home/gwilson/RPi3/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin";
 export HOME="/home/gwilson"; LANG=C git -c core.fsyncobjectfiles=0 clone 
--bare --mirror http://codereview.qt-project.org/qt/qtdeviceutilities 
/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities
 --progress failed with exit code 128, output:
Cloning into bare repository 
'/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities'...
fatal: unable to access 
'https://codereview.qt-project.org/qt/qtdeviceutilities/': server certificate 
verification failed. CAfile: 
/usr/share/ca-certificates/cert_Decryption-Certificate.pem CRLfile: none

ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher 
failure for URL: 
'git://codereview.qt-project.org/qt/qtdeviceutilities;nobranch=1;protocol=http'.
 Unable to fetch URL from any source.
ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Function 
failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/qtdeviceutilities/5.9.1+gitAUTOINC+48fb704e64-r0/temp/log.do_fetch.8128
ERROR: Task 
(/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/meta-boot2qt/recipes-qt/qt5/qtdeviceutilities.bb:do_fetch)
 failed with exit code '1'

So it looks like:

qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch

is what's running.




From: Andre McCurdy 
Sent: Wednesday, September 6, 2017 6:34:07 PM
To: Greg Wilson-Lindberg
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Working behind a Palo Alto firewall/proxy

On Wed, Sep 6, 2017 at 2:42 PM, Greg Wilson-Lindberg
 wrote:
> Hi List,
>
> Does anybody have any experience trying to run Yocto behind a Palo Alto
> firewall. The Palo Alto firewall basically works as a Man in the Middle
> system, it hands out its own certificate to boxes behind it and then
> decrypts and re-encrypts traffic going through it. The Palo Alto box is
> supposed to act as a transparent Proxy.
>
> I'm getting an error that the 'server certificate verification failed' about
> an hour into a yocto build. The certificate that the Palo Alto box is
> sending to my system is self-signed so will fail if checked for a valid root
> CA, and also is not from whatever site is being downloaded from.

Which site is being downloaded from and at which point in the build
(ie which recipe and task) ?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Working behind a Palo Alto firewall/proxy

2017-09-07 Thread Mark Hatle 
I've had a customer with a similar problem.  The way they resolved it was to
download the certification from their proxy and add it to their system as a
known certificate.

Sorry I don't have any more details then that, but maybe that can spark someone
who knows the actual steps to be able to comment.

--Mark

On 9/7/17 11:28 AM, Greg Wilson-Lindberg wrote:
> Hi Andre,
> 
> 
> Here is the complete error output:
> 
> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher
> failure: Fetch command export
> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-9ReQWXYEk1"; export
> SSH_AUTH_SOCK="/run/user/1000/keyring-4PGABB/ssh"; export
> PATH="/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/raspberrypi3/usr/bin/crossscripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/bitbake/bin:/home/gwilson/TEE:/home/gwilson/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/microchip/xc32/v1.34/bin:/home/gwilson/RPi3/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin";
> export HOME="/home/gwilson"; LANG=C git -c core.fsyncobjectfiles=0 clone 
> --bare
> --mirror http://codereview.qt-project.org/qt/qtdeviceutilities
> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities
> --progress failed with exit code 128, output:
> Cloning into bare repository
> '/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities'...
> fatal: unable to access
> 'https://codereview.qt-project.org/qt/qtdeviceutilities/': server certificate
> verification failed. CAfile:
> /usr/share/ca-certificates/cert_Decryption-Certificate.pem CRLfile: none
> 
> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher
> failure for URL:
> 'git://codereview.qt-project.org/qt/qtdeviceutilities;nobranch=1;protocol=http'.
> Unable to fetch URL from any source.
> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Function
> failed: base_do_fetch
> ERROR: Logfile of failure stored in:
> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/qtdeviceutilities/5.9.1+gitAUTOINC+48fb704e64-r0/temp/log.do_fetch.8128
> ERROR: Task
> (/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/meta-boot2qt/recipes-qt/qt5/qtdeviceutilities.bb:do_fetch)
> failed with exit code '1'
> 
> So it looks like:
> 
> qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch
> 
> is what's running.
> 
> 
> 
> 
> *From:* Andre McCurdy 
> *Sent:* Wednesday, September 6, 2017 6:34:07 PM
> *To:* Greg Wilson-Lindberg
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Working behind a Palo Alto firewall/proxy
>  
> On Wed, Sep 6, 2017 at 2:42 PM, Greg Wilson-Lindberg
>  wrote:
>> Hi List,
>>
>> Does anybody have any experience trying to run Yocto behind a Palo Alto
>> firewall. The Palo Alto firewall basically works as a Man in the Middle
>> system, it hands out its own certificate to boxes behind it and then
>> decrypts and re-encrypts traffic going through it. The Palo Alto box is
>> supposed to act as a transparent Proxy.
>>
>> I'm getting an error that the 'server certificate verification failed' about
>> an hour into a yocto build. The certificate that the Palo Alto box is
>> sending to my system is self-signed so will fail if checked for a valid root
>> CA, and also is not from whatever site is being downloaded from.
> 
> Which site is being downloaded from and at which point in the build
> (ie which recipe and task) ?
> 
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Working behind a Palo Alto firewall/proxy

2017-09-07 Thread Khem Raj 
you can try adding following to ~/.gitconfig

[http]
sslverify = false

On Thu, Sep 7, 2017 at 9:31 AM, Mark Hatle  wrote:
> I've had a customer with a similar problem.  The way they resolved it was to
> download the certification from their proxy and add it to their system as a
> known certificate.
>
> Sorry I don't have any more details then that, but maybe that can spark 
> someone
> who knows the actual steps to be able to comment.
>
> --Mark
>
> On 9/7/17 11:28 AM, Greg Wilson-Lindberg wrote:
>> Hi Andre,
>>
>>
>> Here is the complete error output:
>>
>> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher
>> failure: Fetch command export
>> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-9ReQWXYEk1"; export
>> SSH_AUTH_SOCK="/run/user/1000/keyring-4PGABB/ssh"; export
>> PATH="/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/raspberrypi3/usr/bin/crossscripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/bitbake/bin:/home/gwilson/TEE:/home/gwilson/
 
bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/microchip/xc32/v1.34/bin:/home/gwilson/RPi3/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin";
>> export HOME="/home/gwilson"; LANG=C git -c core.fsyncobjectfiles=0 clone 
>> --bare
>> --mirror http://codereview.qt-project.org/qt/qtdeviceutilities
>> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities
>> --progress failed with exit code 128, output:
>> Cloning into bare repository
>> '/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities'...
>> fatal: unable to access
>> 'https://codereview.qt-project.org/qt/qtdeviceutilities/': server certificate
>> verification failed. CAfile:
>> /usr/share/ca-certificates/cert_Decryption-Certificate.pem CRLfile: none
>>
>> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher
>> failure for URL:
>> 'git://codereview.qt-project.org/qt/qtdeviceutilities;nobranch=1;protocol=http'.
>> Unable to fetch URL from any source.
>> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Function
>> failed: base_do_fetch
>> ERROR: Logfile of failure stored in:
>> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/qtdeviceutilities/5.9.1+gitAUTOINC+48fb704e64-r0/temp/log.do_fetch.8128
>> ERROR: Task
>> (/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/meta-boot2qt/recipes-qt/qt5/qtdeviceutilities.bb:do_fetch)
>> failed with exit code '1'
>>
>> So it looks like:
>>
>> qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch
>>
>> is what's running.
>>
>>
>>
>> 
>> *From:* Andre McCurdy 
>> *Sent:* Wednesday, September 6, 2017 6:34:07 PM
>> *To:* Greg Wilson-Lindberg
>> *Cc:* yocto@yoctoproject.org
>> *Subject:* Re: [yocto] Working behind a Palo Alto firewall/proxy
>>
>> On Wed, Sep 6, 2017 at 2:42 PM, Greg Wilson-Lindberg
>>  wrote:
>>> Hi List,
>>>
>>> Does anybody have any experience trying to run Yocto behind a Palo Alto
>>> firewall. The Palo Alto firewall basically works as a Man in the Middle
>>> system, it hands out its own certificate to boxes behind it and then
>>> decrypts and re-encrypts traffic going through it. The Palo Alto box is
>>> supposed to act as a transparent Proxy.
>>>
>>> I'm getting an error that the 'server certificate verification failed' about
>>> an hour into a yocto build. The certificate that the Palo Alto box is
>>> sending to my system is self-signed so will fail if checked for a valid root
>>> CA, and also is not from whatever site is being downloaded from.
>>
>> Which site is being downloaded from and at which point in the build
>> (ie which recipe and task) ?
>>
>>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [patchwork][PATCH] patchwork/templates/patchwork/series.html: Add link column

2017-09-07 Thread Jose Lamego 
Clicking on a patch name in Series view displays the patch at
the botton section in same page, but there is no easy way to
get a direct link to the patch, for example: to share the link.

This change includes the column "Link" where a direct link to the
patch is displayed and labeled with the patch id, that can be copied
or clicked to displayed the patch detail on a new tab.

[YOCTO #11888]

Signed-off-by: Jose Lamego 
---
 patchwork/templates/patchwork/series.html | 4 
 1 file changed, 4 insertions(+)

diff --git a/patchwork/templates/patchwork/series.html 
b/patchwork/templates/patchwork/series.html
index 6c374f7..6c4608b 100644
--- a/patchwork/templates/patchwork/series.html
+++ b/patchwork/templates/patchwork/series.html
@@ -110,6 +110,7 @@ function toggle_headers(link_id, headers_id)
 
   {% endif %}
   Name
+  Link
   Submitter
   State
 
@@ -126,6 +127,9 @@ function toggle_headers(link_id, headers_id)
 {{ patch.name|default:"[no subject]"|truncatechars:100 
}}
+{{ patch.id }}
 {{ patch.submitter|personify:project }}
 {{ patch.state }}
   
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Working behind a Palo Alto firewall/proxy

2017-09-07 Thread Greg Wilson-Lindberg 
Hi Mark,


Unfortunately, in this case the certificate has already been added to the 
system, necessary to get https working.


Greg


From: Mark Hatle 
Sent: Thursday, September 7, 2017 9:31:02 AM
To: Greg Wilson-Lindberg; Andre McCurdy
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Working behind a Palo Alto firewall/proxy

I've had a customer with a similar problem.  The way they resolved it was to
download the certification from their proxy and add it to their system as a
known certificate.

Sorry I don't have any more details then that, but maybe that can spark someone
who knows the actual steps to be able to comment.

--Mark

On 9/7/17 11:28 AM, Greg Wilson-Lindberg wrote:
> Hi Andre,
>
>
> Here is the complete error output:
>
> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher
> failure: Fetch command export
> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-9ReQWXYEk1"; export
> SSH_AUTH_SOCK="/run/user/1000/keyring-4PGABB/ssh"; export
> PATH="/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/raspberrypi3/usr/bin/crossscripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/bitbake/bin:/home/gwilson/TEE:/home/gwilson/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/microchip/xc32/v1.34/bin:/home/gwilson/RPi3/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin";
> export HOME="/home/gwilson"; LANG=C git -c core.fsyncobjectfiles=0 clone 
> --bare
> --mirror http://codereview.qt-project.org/qt/qtdeviceutilities
> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities
> --progress failed with exit code 128, output:
> Cloning into bare repository
> '/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/codereview.qt-project.org.qt.qtdeviceutilities'...
> fatal: unable to access
> 'https://codereview.qt-project.org/qt/qtdeviceutilities/': server certificate
> verification failed. CAfile:
> /usr/share/ca-certificates/cert_Decryption-Certificate.pem CRLfile: none
>
> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Fetcher
> failure for URL:
> 'git://codereview.qt-project.org/qt/qtdeviceutilities;nobranch=1;protocol=http'.
> Unable to fetch URL from any source.
> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch: Function
> failed: base_do_fetch
> ERROR: Logfile of failure stored in:
> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/qtdeviceutilities/5.9.1+gitAUTOINC+48fb704e64-r0/temp/log.do_fetch.8128
> ERROR: Task
> (/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/meta-boot2qt/recipes-qt/qt5/qtdeviceutilities.bb:do_fetch)
> failed with exit code '1'
>
> So it looks like:
>
> qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch
>
> is what's running.
>
>
>
> 
> *From:* Andre McCurdy 
> *Sent:* Wednesday, September 6, 2017 6:34:07 PM
> *To:* Greg Wilson-Lindberg
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Working behind a Palo Alto firewall/proxy
>
> On Wed, Sep 6, 2017 at 2:42 PM, Greg Wilson-Lindberg
>  wrote:
>> Hi List,
>>
>> Does anybody have any experience trying to run Yocto behind a Palo Alto
>> firewall. The Palo Alto firewall basically works as a Man in the Middle
>> system, it hands out its own certificate to boxes behind it and then
>> decrypts and re-encrypts traffic going through it. The Palo Alto box is
>> supposed to act as a transparent Proxy.
>>
>> I'm getting an error that the 'server certificate verification failed' about
>> an hour into a yocto build. The certificate that the Palo Alto box is
>> sending to my system is self-signed so will fail if checked for a valid root
>> CA, and also is not from whatever site is being downloaded from.
>
> Which site is being downloaded from and at which point in the build
> (ie which recipe and task) ?
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Working behind a Palo Alto firewall/proxy

2017-09-07 Thread Greg Wilson-Lindberg 
That did the trick,
Thanks,
Greg

> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Thursday, September 07, 2017 9:52 AM
> To: Mark Hatle 
> Cc: Greg Wilson-Lindberg ; Andre McCurdy
> ; yocto@yoctoproject.org
> Subject: Re: [yocto] Working behind a Palo Alto firewall/proxy
> 
> you can try adding following to ~/.gitconfig
> 
> [http]
> sslverify = false
> 
> On Thu, Sep 7, 2017 at 9:31 AM, Mark Hatle 
> wrote:
> > I've had a customer with a similar problem.  The way they resolved it
> > was to download the certification from their proxy and add it to their
> > system as a known certificate.
> >
> > Sorry I don't have any more details then that, but maybe that can
> > spark someone who knows the actual steps to be able to comment.
> >
> > --Mark
> >
> > On 9/7/17 11:28 AM, Greg Wilson-Lindberg wrote:
> >> Hi Andre,
> >>
> >>
> >> Here is the complete error output:
> >>
> >> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch:
> >> Fetcher
> >> failure: Fetch command export
> >> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-
> 9ReQWXYEk1"; export
> >> SSH_AUTH_SOCK="/run/user/1000/keyring-4PGABB/ssh"; export
> >> PATH="/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-
> raspberrypi3/tmp/sy
> >> sroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/bui
> >> ld-raspberrypi3/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/gwi
> >> lson/Qt-5.9/Yocto-build-RPi3/sources/poky/scripts:/home/gwilson/Qt-5.
> >> 9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/usr/b
> >> in/arm-poky-linux-gnueabi:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build
> >> -raspberrypi3/tmp/sysroots/raspberrypi3/usr/bin/crossscripts:/home/gw
> >> ilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-
> >> linux/usr/sbin:/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberryp
> >> i3/tmp/sysroots/x86_64-linux/usr/bin:/home/gwilson/Qt-5.9/Yocto-build
> >> -RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux/sbin:/home/gwilson
> >> /Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/tmp/sysroots/x86_64-linux
> >> /bin:/home/gwilson/Qt-5.9/Yocto-build-
> RPi3/sources/poky/scripts:/home
> >> /gwilson/Qt-5.9/Yocto-build-RPi3/sources/poky/bitbake/bin:/home/gwils
> >> on/TEE:/home/gwilson/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/us
> >> r/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/microchip/xc32/v1.3
> >> 4/bin:/home/gwilson/RPi3/tools/arm-bcm2708/gcc-linaro-arm-linux-
> gnuea
> >> bihf-raspbian-x64/bin"; export HOME="/home/gwilson"; LANG=C git -c
> >> core.fsyncobjectfiles=0 clone --bare --mirror
> >> http://codereview.qt-project.org/qt/qtdeviceutilities
> >> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-raspberrypi3/../downloads
> >> /git2/codereview.qt-project.org.qt.qtdeviceutilities
> >> --progress failed with exit code 128, output:
> >> Cloning into bare repository
> >> '/home/gwilson/Qt-5.9/Yocto-build-RPi3/build-
> raspberrypi3/../downloads/git2/codereview.qt-
> project.org.qt.qtdeviceutilities'...
> >> fatal: unable to access
> >> 'https://codereview.qt-project.org/qt/qtdeviceutilities/': server
> >> certificate verification failed. CAfile:
> >> /usr/share/ca-certificates/cert_Decryption-Certificate.pem CRLfile:
> >> none
> >>
> >> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch:
> >> Fetcher failure for URL:
> >> 'git://codereview.qt-
> project.org/qt/qtdeviceutilities;nobranch=1;protocol=http'.
> >> Unable to fetch URL from any source.
> >> ERROR: qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch:
> >> Function
> >> failed: base_do_fetch
> >> ERROR: Logfile of failure stored in:
> >> /home/gwilson/Qt-5.9/Yocto-build-RPi3/build-
> raspberrypi3/tmp/work/cor
> >> texa7hf-neon-vfpv4-poky-linux-gnueabi/qtdeviceutilities/5.9.1+gitAUTO
> >> INC+48fb704e64-r0/temp/log.do_fetch.8128
> >> ERROR: Task
> >> (/home/gwilson/Qt-5.9/Yocto-build-RPi3/sources/meta-boot2qt/recipes-
> q
> >> t/qt5/qtdeviceutilities.bb:do_fetch)
> >> failed with exit code '1'
> >>
> >> So it looks like:
> >>
> >> qtdeviceutilities-5.9.1+gitAUTOINC+48fb704e64-r0 do_fetch
> >>
> >> is what's running.
> >>
> >>
> >>
> >> -
> >> ---
> >> *From:* Andre McCurdy 
> >> *Sent:* Wednesday, September 6, 2017 6:34:07 PM
> >> *To:* Greg Wilson-Lindberg
> >> *Cc:* yocto@yoctoproject.org
> >> *Subject:* Re: [yocto] Working behind a Palo Alto firewall/proxy
> >>
> >> On Wed, Sep 6, 2017 at 2:42 PM, Greg Wilson-Lindberg
> >>  wrote:
> >>> Hi List,
> >>>
> >>> Does anybody have any experience trying to run Yocto behind a Palo
> >>> Alto firewall. The Palo Alto firewall basically works as a Man in
> >>> the Middle system, it hands out its own certificate to boxes behind
> >>> it and then decrypts and re-encrypts traffic going through it. The
> >>> Palo Alto box is supposed to act as a transparent Proxy.
> >>>
> >>> I'm getting an error that the 'server certificate verification
> >>> failed' about an hour into

Re: [yocto] The basehash value changed from...

2017-09-07 Thread Max Krummenacher 
Hi Zoran

Am Donnerstag, den 07.09.2017, 09:37 +0200 schrieb Zoran Stojsavljevic:
> While re-compiling the whole YOCTO load for freescale i.MX6, where I have
> added Qt5 layers (and it failed many times, so I needed to do some tricks
> there), I encounter the following warning (in *ORANGE*) and error (in *RED*)
> while finishing the build:
> 
> *WARNING: Duplicate inclusion for
> /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-bsp-
> common/conf/tdx_version.conf
> in
> /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-
> images/images/tdx-image-fstype.inc*
> *ERROR: When reparsing
> /home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-
> images/images/angstrom-lxde-image.bb.do_image_teziimg,
> the basehash value changed from b7b4f312b8b657bfdd068ebd8e2dd104 to
> 1e71714a9c01964cdc724c52290abee4. The metadata is not deterministic and
> this needs to be fixed.*
> NOTE: Tasks Summary: Attempted 7415 tasks of which 7394 didn't need to be
> rerun and all succeeded.

Please note the '... and all succeeded'. So the basehash error did not break the
build.

I think the basehash error is due to the use of the DATE variable and
that the following commit fixes it in master:
http://cgit.openembedded.org/openembedded-core/commit/?id=4af13a4855c74cea9cf6c168fd73165d7094bf93

However Stefan is still in the process of backporting said commit, so you still
see the error in morty.
http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141582.html

Max

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ERROR: fsl-image-qt5: Recipe file does not have license file information (LIC_FILES_CHKSUM)

2017-09-07 Thread Paritosh Singh 
Dear Team,


I have successfully used yocto for fsl-image-qt5, but the rootfs generated from 
this is 1.1 Gb.

In order reduce the size of generated rootfs I have removed "require 
recipes-fsl/images/fsl-image-gui.bb" line from fsl-image-qt5. After that I am 
getting this error

ERROR: fsl-image-qt5: Recipe file does not have license file information 
(LIC_FILES_CHKSUM)
ERROR: Licensing Error: LIC_FILES_CHKSUM does not match, please fix
ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in: 
/fsl-release-bsp/build-imx7/tmp/work/cortexa7hf-vfp-neon-poky-linux-gnueabi/fsl-image-qt5/1.0-r0/temp/log.do_configure.28946
ERROR: Task 5 
(/fsl-release-bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/images/fsl-image-qt5.bb,
 do_configure) failed with exit code '1'

Can someone help me out regarding this.

Regards,
Paritosh Singh

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto