Re: [yocto] [PATCH][yocto-autobuilder] nigthly-qa-*, nigthly-rpm*: Move RunSanityTests before SendErrorReport

2016-09-19 Thread Joshua Lock 
On Sun, 2016-09-18 at 13:05 -0500, Aníbal Limón wrote:
> If RunSanityTests executes after SendErrorReport and fails, the error
> report was not send to the errors.yp.org server.

Pushed, thanks.

Joshua

> Signed-off-by: Aníbal Limón 
> ---
>  buildset-config.controller/nightly-qa-extras.conf   | 4 ++--
>  buildset-config.controller/nightly-qa-logrotate.conf| 6 ++
>  buildset-config.controller/nightly-qa-pam.conf  | 5 ++---
>  buildset-config.controller/nightly-qa-skeleton.conf | 5 ++---
>  buildset-config.controller/nightly-qa-systemd.conf  | 4 ++--
>  buildset-config.controller/nightly-qa-targetbuilds.conf | 6 +++---
>  buildset-config.controller/nightly-rpm-non-rpm.conf | 4 ++--
>  buildset-config.controller/nightly-rpm.conf | 4 ++--
>  8 files changed, 17 insertions(+), 21 deletions(-)
> 
> diff --git a/buildset-config.controller/nightly-qa-extras.conf
> b/buildset-config.controller/nightly-qa-extras.conf
> index 2ec7b50..f796bb1 100644
> --- a/buildset-config.controller/nightly-qa-extras.conf
> +++ b/buildset-config.controller/nightly-qa-extras.conf
> @@ -18,6 +18,6 @@ steps: [{'SetDest':{}},
>  'distro': 'poky', 'buildhistory' :
> False,
>  'atextappend' : '\nROOT_HOME =
> "/root"\n'}},
>  {'BuildImages': {'images': 'core-image-minimal'}},
> +{'RunSanityTests': {'images': 'core-image-minimal'}},
>  {'DownloadErrorReports': {}},
> -{'SendErrorReport': {}},
> -{'RunSanityTests': {'images': 'core-image-minimal'}}]
> +{'SendErrorReport': {}}]
> diff --git a/buildset-config.controller/nightly-qa-logrotate.conf
> b/buildset-config.controller/nightly-qa-logrotate.conf
> index 41dd135..1545509 100644
> --- a/buildset-config.controller/nightly-qa-logrotate.conf
> +++ b/buildset-config.controller/nightly-qa-logrotate.conf
> @@ -13,8 +13,6 @@ steps: [{'SetDest':{}},
>  'atextappend' : '\nIMAGE_INSTALL_append
> = " logrotate"\n'}},
>  {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
>  {'BuildImages': {'images': 'core-image-sato'}},
> +{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'logrotate'}},
>  {'DownloadErrorReports': {}},
> -{'SendErrorReport': {}},
> -{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'logrotate'}}]
> -
> -
> +{'SendErrorReport': {}}]
> diff --git a/buildset-config.controller/nightly-qa-pam.conf
> b/buildset-config.controller/nightly-qa-pam.conf
> index 5cec2c8..3fdb76f 100644
> --- a/buildset-config.controller/nightly-qa-pam.conf
> +++ b/buildset-config.controller/nightly-qa-pam.conf
> @@ -13,7 +13,6 @@ steps: [{'SetDest':{}},
>  'atextappend' :
> '\nDISTRO_FEATURES_append = " pam"\n'}},
>  {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
>  {'BuildImages': {'images': 'core-image-sato'}},
> +{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'pam'}},
>  {'SendErrorReport': {}},
> -{'DownloadErrorReports': {}},
> -{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'pam'}}]
> -
> +{'DownloadErrorReports': {}}]
> diff --git a/buildset-config.controller/nightly-qa-skeleton.conf
> b/buildset-config.controller/nightly-qa-skeleton.conf
> index c29ca7b..9ac4c5e 100644
> --- a/buildset-config.controller/nightly-qa-skeleton.conf
> +++ b/buildset-config.controller/nightly-qa-skeleton.conf
> @@ -13,7 +13,6 @@ steps: [{'SetDest':{}},
>  'atextappend' : '\nIMAGE_INSTALL_append
> = " service hello-mod"\n'}},
>  {'CreateBBLayersConf': {'buildprovider' : 'yocto',
> 'layerdirs': ['meta-skeleton']}},
>  {'BuildImages': {'images': 'core-image-sato'}},
> +{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'skeletoninit'}},
>  {'DownloadErrorReports': {}},
> -{'SendErrorReport': {}},
> -{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'skeletoninit'}}]
> -
> +{'SendErrorReport': {}}]
> diff --git a/buildset-config.controller/nightly-qa-systemd.conf
> b/buildset-config.controller/nightly-qa-systemd.conf
> index 662caa6..bb6da0b 100644
> --- a/buildset-config.controller/nightly-qa-systemd.conf
> +++ b/buildset-config.controller/nightly-qa-systemd.conf
> @@ -27,6 +27,6 @@ steps: [{'SetDest':{}},
>  'buildhistory' : False, 'distro':
> 'poky',
>  'initmgr' : 'systemd'}},
>  {'BuildImages': {'images': 'core-image-sato'}},
> +{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'systemd'}},
>  {'DownloadErrorReports': {}},
> -{'SendErrorReport': {}},
> -{'RunSanityTests': {'images': 'core-image-sato',
> 'suitesappend' : 'systemd'}}]
> +{'SendErrorReport': {}}]
>

Re: [yocto] build ntp with openssl support

2016-09-19 Thread Oliver Graute 
On 16/09/16, Andre McCurdy wrote:
> On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute  
> wrote:
> > Hello,
> >
> > how can I build ntp with openssl support?
> >
> > I already created a ntp_%.bbappend file to extend the recipe ntp_4.2.8p4.bb.
> >
> > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> 
> You don't really need this line unless you are adding a file to
> SRC_URI or replacing a file already in SRC_URI with your own version.
> 
> > PACKAGECONFIG += "openssl"
> 
> This will enable openssl, but it will also disable all the default
> PACKAGECONFIG options (cap, debug and refclocks) which is probably not
> what you want. Try this instead:
> 
>   PACKAGECONFIG_append = " openssl"
> 
> Note the space between " and openssl. It's required.

ok now I see the right configure script options during the configuration
of the ntp build.

--with-openssl-libdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
--with-openssl-incdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
--with-crypto

But ntp is still build without openssl support. The configure scripts
can't find the relevant openssl stuff.

configure:34762: checking for openssl library directory
configure:34802: result: no
configure:34807: WARNING: libcrypto and libssl not found in any of 
/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
configure:34811: checking for openssl include directory
configure:34833: result: 
/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
configure:34877: checking if we will use crypto
configure:34879: result: no
configure:35109: checking if we want to use OpenSSL's crypto random (if 
available)
configure:35119: result: yes

some clue whats wrong here?

Best regards,

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

Re: [yocto] [toaster] import config

2016-09-19 Thread Barros Pena, Belen 


On 16/09/2016 16:12, "yocto-boun...@yoctoproject.org on behalf of Mathieu
Allard"  wrote:

>Hi!
>
>It maybe is a naive question and I assume it's not possible because I
>didn't find anything related in the manual.
>
>Is it possible to launch a toaster instance on an already
>command-line-setup build?

If you are using the 2.1 release (krogoth), you can start a build from the
command line from your build directory as you would normally do without
Toaster. Toaster will monitor the build and store all the information
about it in a special project we've called "Command Line Builds".

This means you can configure the build system using config files, instead
of Toaster, and still use the build reporting capabilities of Toaster if
that's what you are after. You just need to make sure Toaster is running
before you issue the bitbake command.

I hope this makes sense.

Cheers

Belén


>Like inheriting the toaster bbclass and maybe some magic trick?
>
>Or am I stuck in reconfiguring everything manually through the web
>interface?
>
>Now that I have some working builds, I just wanted to know is there is a
>quick way to get some overview over it on our local network, and to
>quickly build my application again when I have an update.
>
>Otherwise I'll just hack some cheap script to launch a remote rebuild of
>my package when I need it.
>-- 
>___
>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] [meta-intel][Galileo] Kernel configuration isn't applied on linux-yocto-rt

2016-09-19 Thread Claudius Heine 
Hi,

in order to isolate this issue I removed every layer with the exception
of poky and compiled linux-yocto-rt for "qemux86" with success.
(CONFIG_64BIT was set to n)

Then I added the meta-intel layer and compiled the real time kernel for
"intel-core2-32" also with success. (CONFIG_64BIT=n)

However choosing "intel-quark" resulted in the aforementioned error.
(CONFIG_64BIT=y)

So I suppose its a meta-intel upstream bug.

My Layers:

poky: "krogoth:aad7166704021d82ad3a5ec468552f8f10360d41"
meta-intel: 141e71af3c59f9bd5d45029a418de2e1ce90aacd
  with reverted: 7d00922e1cd3caabb8046e68a6107b9f4f3f1d34
  because this poky version only supports gummiboot not systemd-boot

regards,
Claudius


-- 
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: c...@denx.de
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH v2] samhain: 4.1.4 -> 4.1.5

2016-09-19 Thread Wang Xin 
1) Upgrade samhain from 4.1.4 to 4.1.5.
2) Add TARGET_CC_ARCH.Fix error.
ERROR: samhain-server-4.1.5-r0 do_package_qa: QA Issue: No GNU_HASH in the 
elf binary: 
'/yocto/work001/fnst/wangx/poky/build/tmp/work/i586-poky-linux/samhain-server/4.1.5-r0/packages-split/samhain-server/usr/sbin/yule_setpwd'
No GNU_HASH in the elf binary: 
'/yocto/work001/fnst/wangx/poky/build/tmp/work/i586-poky-linux/samhain-server/4.1.5-r0/packages-split/samhain-server/usr/sbin/yulectl'
 [ldflags]

Signed-off-by: Wang Xin 
---
 .../samhain/{samhain-client_4.1.4.bb => samhain-client_4.1.5.bb}  | 0
 .../samhain/{samhain-server_4.1.4.bb => samhain-server_4.1.5.bb}  | 2 ++
 recipes-security/samhain/samhain.inc  | 4 ++--
 3 files changed, 4 insertions(+), 2 deletions(-)
 rename recipes-security/samhain/{samhain-client_4.1.4.bb => 
samhain-client_4.1.5.bb} (100%)
 rename recipes-security/samhain/{samhain-server_4.1.4.bb => 
samhain-server_4.1.5.bb} (97%)

diff --git a/recipes-security/samhain/samhain-client_4.1.4.bb 
b/recipes-security/samhain/samhain-client_4.1.5.bb
similarity index 100%
rename from recipes-security/samhain/samhain-client_4.1.4.bb
rename to recipes-security/samhain/samhain-client_4.1.5.bb
diff --git a/recipes-security/samhain/samhain-server_4.1.4.bb 
b/recipes-security/samhain/samhain-server_4.1.5.bb
similarity index 97%
rename from recipes-security/samhain/samhain-server_4.1.4.bb
rename to recipes-security/samhain/samhain-server_4.1.5.bb
index df78f63..0d76b9a 100644
--- a/recipes-security/samhain/samhain-server_4.1.4.bb
+++ b/recipes-security/samhain/samhain-server_4.1.5.bb
@@ -21,6 +21,8 @@ PACKAGECONFIG[acl] = " --enable-posix-acl , 
--disable-posix-acl"
 
 SRC_URI += "file://samhain-server-volatiles"
 
+TARGET_CC_ARCH += "${LDFLAGS}"
+
 EXTRA_OECONF += " \
 --with-config-file=REQ_FROM_SERVER/etc/samhainrc \
 --with-data-file=REQ_FROM_SERVER/var/lib/samhain/samhain_file \
diff --git a/recipes-security/samhain/samhain.inc 
b/recipes-security/samhain/samhain.inc
index 907f431..5bf2ee7 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -9,8 +9,8 @@ SRC_URI = 
"http://la-samhna.de/archive/samhain_signed-${PV}.tar.gz \
   file://${INITSCRIPT_NAME}.default \
  "
 
-SRC_URI[md5sum] = "1ab697b7000d0a272d9ade05bb1bc6e0"
-SRC_URI[sha256sum] = 
"32ee7477af11d9f2f64f30b9cb316c351897c1c994c7b98b0ef17fc0ca5e1d1a"
+SRC_URI[md5sum] = "bdb6d2653d706f3180e37ef3d95c824d"
+SRC_URI[sha256sum] = 
"4ff4c38765c942abbaac2577df4c8c4940482a1bffc4a719f181c4fca6f173a7"
 
 S = "${WORKDIR}/samhain-${PV}"
 
-- 
2.7.4



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