[yocto] [meta-cgl][PATCH] poky-cgl: avoid installing multiple syslogs

From: Jackie Huang do_rootfs fails if multiple syslogs are installed: | Error: package syslog-ng-3.8.1-r0.i586 conflicts with sysklogd provided by sysklogd-1.5.1-r0.i586 core-image-cgl requires packagegroup-core-full-cmdline which depends on VIRTUAL-RUNTIME_syslog (default to sysklogd), so set

[yocto] [meta-cgl][PATCH 0/4] resource-agents: update to 4.0.1 and several fixes

From: Jackie Huang -- The following changes since commit c0afa706e9cdb650c0e8bb79f503743632350b00: core-image-cgl: Remove ROOTFS_PKGMANAGE_BOOTSTRAP (2017-05-24 14:19:13 +0200) are available in the git repository at: https://github.com/jackiehjm/meta-cgl.git jhuang0/up_resource-agents_1706

[yocto] [meta-cgl][PATCH 1/4] resource-agents: fix dependencies

From: Jackie Huang * inherit pkgconfig or configure fails with: | checking for pkg-config... no | configure: error: You need pkgconfig installed in order to build * Add missing runtime dependencies for: - many tools and scripts need bash and perl. - lvm.sh requires: lvm2 - ip.sh requir

[yocto] [meta-cgl][PATCH 3/4] resource-agents: fix builds error when S != B

From: Jackie Huang It fails to find fs.sh.in when srddir and builddir are not the same: make[5]: Entering directory '/path/to/builddir/rgmanager/src/resources' cat fs.sh.in | sed \ -e 's#@''LOGDIR@#/var/log/cluster#g' \ > fs.sh.out cat: fs.sh.in: No such file or directorychmod +x fs.

[yocto] [meta-cgl][PATCH 4/4] resource-agents: update to version 4.0.1

From: Jackie Huang Signed-off-by: Jackie Huang --- .../{resource-agents_3.9.7.bb => resource-agents_4.0.1.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-cgl-common/recipes-cgl/cluster-resource-agents/{resource-agents_3.9.7.bb => resource-agents_4.0.1.bb}

[yocto] [meta-cgl][PATCH 2/4] resource-agents: fix install-sh not found

From: Jackie Huang Fix configure.ac to cope with new autoconf. Recent autoconfs generate a bad configure when AM_INIT_AUTOMAKE is called as late as it was, ending up thinking that the am_aux_dir is pwd at the start of the build. Move it up to under AC_INIT to fix that. configure.ac calls AM_INIT

[yocto] [meta-zulu-java][PATCH] zulu-jdk: move files to designated packages

The current zulu-jdk package includes many big files that are not required to run java-programs on target devices. This patch avoids that zulu-jdk acquires too much space on the target device. Signed-off-by: Sven Ebenfeld --- recipes-devtools/zulu-ezdk-arm-hflt.bb | 14 ++ recipes-de

[yocto] [meta-zulu-java][PATCH] zulu-jdk: move files to designated packages

The current zulu-jdk package includes many big files that are not required to run java-programs on target devices. This patch avoids that zulu-jdk acquires too much space on the target device. Signed-off-by: Sven Ebenfeld --- recipes-devtools/zulu-ezdk-arm-hflt.bb | 14 ++ recipes-de

Re: [yocto] [yocto-autobuilder][PATCH] forcebuild: allow build with default options

On Thu, 2017-06-01 at 12:32 -0500, Jose Lamego wrote: > From: Anibal Limon > > A forced build fails if no options are passed through command > line (using "-o OPTIONS"). > > This change allows build to use default options if none are passed > at the command line. Useful. Merged, thanks! Joshua

Re: [yocto] Problems to build xen-guest-image-minimal

On Wed, May 31, 2017 at 10:13 AM, Khem Raj wrote: > > On Wed, May 31, 2017 at 12:22 AM Pello Heriz < > pello.he...@alumni.mondragon.edu> wrote: > >> Hi, >> >> I'm trying to build xen-guest-image-minimal with master branch of Yocto, >> but I keep stuck in the next error: >> >> bitbake xen-guest-im

[yocto] [yocto-autobuilder][PATCH 1/5] buildsteps/BuildImages: Setproperty BUILDIMAGES

In certain situations is need to know what images was built for example the DAFT executes flashing over certain image. [YOCTO #10604] Signed-off-by: Aníbal Limón --- lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lib/pyth

[yocto] [yocto-autobuilder][PATCH 2/5] buildsteps/RunSanityTests: Add support for simpleremote target

The testimage class supports a simpleremote target specifying the server and target ip to run tests over SSH. The main usage of this will in conjunction with the DAFT to make tests on real HW. [YOCTO #10604] Signed-off-by: Aníbal Limón --- .../site-packages/autobuilder/buildsteps/RunSanityTest

[yocto] [yocto-autobuilder][PATCH 3/5] autobuilder/buildsteps: Add DaftGetDevices step

This buildstep will copy the devices configuration from the worker and read it, in order to get daft ip an ssh port, to use later in RunSanityTests [YOCTO #10604] Signed-off-by: Aníbal Limón Signed-off-by: Monserrat Sedeno Signed-off-by: Edwin Plauchu --- config/autobuilder.conf.example

[yocto] [yocto-autobuilder][PATCH 4/5] autobuilder/buildsteps: Add DAFTFlash buildstep

This will execute daft flash cycle without reboot and prepare the dut for sanity tests. [YOCTO #10604] Signed-off-by: Aníbal Limón Signed-off-by: Monserrat Sedeno Signed-off-by: Edwin Plauchu --- config/autobuilder.conf.example| 1 + .../autobuilder/buildsteps/DaftFlash.p

[yocto] [yocto-autobuilder][PATCH 5/5] buildset-config.yocto-qa: Add intel-corei7-64-daft buildset

This buildset is for support running sanity tests over a DUT like Minnowboard for the moment only builds core-image-sato, there is a need to make it configurable. Also the listo of the available devices are fixed into the UI as parameters. [YOCTO #10604] Signed-off-by: Aníbal Limón --- buildse

[yocto] [qa-tools][PATCH] testopia_update: Add functionality to list templates

From: Jose Perez Carranza Add support to list available templates per specific releases Signed-off-by: Jose Perez Carranza --- testopia_update.py | 18 -- testopia_update/product/__init__.py | 9 +++-- 2 files changed, 23 insertions(+), 4 deletions(-) dif

Re: [yocto] Why can't I install eudev-hwdb

On 06/01/2017 09:52 AM, Gary Thomas wrote: > On 2017-06-01 15:46, Burton, Ross wrote: >> >> On 1 June 2017 at 14:38, Gary Thomas > > wrote: >> >> Thanks for the suggestion. Sadly, still no go. >> >> >> No idea then. CCing Alejandro... > > Very interesting - I'm bu

[yocto] File permissions on package_ipk.bbclass

Hello, We are using the *package_ipk.bbclass *to create packages for opkg that will be installed on our embedded hardware (target). We are also using Jenkins as a CI server to run bitbake. We have discovered that when we install packages built on Jenkins we get all kinds of file permissions er

Re: [yocto] File permissions on package_ipk.bbclass

On Fri, Jun 2, 2017 at 1:57 PM, Ian Welch wrote: > Hello, > We are using the package_ipk.bbclass to create packages for opkg that > will be installed on our embedded hardware (target). We are also using > Jenkins as a CI server to run bitbake. We have discovered that when we > install package

[yocto] SRCPV and SRC_URI

Hello, I’m writing a new recipe and doing something I think should be simple but instead causes an exception when expanding SRCPV. SRCREV = “” SRC_URI = “git://abc.com/xyz.git ” PV = “1.2+git${SRCPV} The above works fine. Problem is, when I add a patch I get an exception when expa

Re: [yocto] SRCPV and SRC_URI

On 03.06.2017 00:26, Russell Peterson wrote: Hello, I’m writing a new recipe and doing something I think should be simple but instead causes an exception when expanding SRCPV. SRCREV = “” SRC_URI = “git://abc.com/xyz.git” PV = “1.2+git${SRCPV} The above works fine. Problem is,

Re: [yocto] File permissions on package_ipk.bbclass

Thanks Raj. We are looking at using `sudo` but this may have a ripple effect in our other build scripts. I was hoping there was a more elegant way to handle this. We are using version Yocto v1.7 ~Ian On Fri, Jun 2, 2017 at 3:14 PM, Khem Raj wrote: > On Fri, Jun 2, 2017 at 1:57 PM, Ian Welch

[yocto] [ANNOUNCEMENT] meta-intel 7.0 for Yocto Project "pyro" 2.3 now available

All, The meta-intel 7.0 layer for the Yocto Project 2.3 “pyro" release and board support packages are now available for download. Tracy Graydon Intel Corporation meta-intel - repo: git://git.yoctoproject.org/meta-intel branch: pyro tag: 7.0-morty-2.3 hash: 7e8f98aa326f16edd679a9

[yocto] libpam-systemd not built, but enabled in systemd PACKAGECONFIG

That is when building systemd with morty. I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure log. In fact only --enable-split-usr --enable-xz and --enable-nls are set according to the log. None of these are set through PACKAGECONFIG. And everything that is set through

Re: [yocto] libpam-systemd not built, but enabled in systemd PACKAGECONFIG

On Fri, Jun 2, 2017 at 4:51 PM, Ferry Toth wrote: > That is when building systemd with morty. > > I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure > log. > > In fact only --enable-split-usr --enable-xz and --enable-nls are set > according to the log. None of these are set

Re: [yocto] File permissions on package_ipk.bbclass

Hi Ian On Fri, Jun 2, 2017 at 3:52 PM, Ian Welch wrote: > Thanks Raj. > > We are looking at using `sudo` but this may have a ripple effect in our > other build scripts. I was hoping there was a more elegant way to handle > this. > > We are using version Yocto v1.7 > ​pseudo is yocto utility wh

Re: [yocto] SRCPV and SRC_URI

Thanks. My recipe was actually using += instead of _append and I tried various combinations using spaces. Not the issue. The issue turned out to be something about my using patchdir=${S}/x in the file:// statement. I removed the patchdir and no more issues. Wasn’t needed anyway. Thanks for