[OE-core] [PATCH] xserver-nodm-init: option to remove cursor

Add a PACKAGECONFIG option to allow the user to disable the mouse cursor/pointer in the X server. This might be useful where a touchscreen is used. Signed-off-by: Trevor Woerner --- .../recipes-graphics/x11-common/xserver-nodm-init/xserver-nodm.conf.in | 2 +- meta/recipes-graphics/x11-common/xs

[OE-core] [PATCH 3/3] oeqa/runtime/context.py: Add automatic target loading

From: Mariano Lopez This adds automatic target loading for runtime testing. It will look for targets in 'lib/oeqa/core/target' in every layer used in the build. Introspection was used to achieve this functionality, the idea is to load all target modules and they will be registered with registerT

[OE-core] [PATCH 1/3] oeqa: Remove __init__.py files.

From: Mariano Lopez >From python 3.3 and above, if a module path contains an __init__.py file, just that path will be checked for module imports; this behavior makes impossible to extend core functionality using other layers with the current __init__.py files. You can check a more detailed explan

[OE-core] [PATCH 2/3] oeqa/target: Add decorator to register targets

From: Mariano Lopez This adds a way to register targets that can be used with runtime testing. To do this just decorate a target class with registerTarget, and set "targetName" attribute to the name that will be used by TEST_TARGET variable. Signed-off-by: Mariano Lopez --- meta/lib/oeqa/core/

[OE-core] [PATCH 0/3] oeqa/runtime: Import custom targets

From: Mariano Lopez This series allows to import custom targets to be used with runtime testing. Now is possible to have a target in /lib/oeqa/core/target and testimage and testexport can use such target using TEST_TARGET variable. To register a custom target you just need use decorate a target

[OE-core] ✗ patchtest: failure for "[v2,1/4] qemurunner: configura..." and 3 more

== Series Details == Series: "[v2,1/4] qemurunner: configura..." and 3 more Revision: 1 URL : https://patchwork.openembedded.org/series/5974/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been e

[OE-core] [PATCH v2 2/4] oeqa: allow extending qemuparams="..."

Sometimes it is useful to reconfigure the qemu virtual machine directly. runqemu has the "qemuparams" parameter for that, and the underlying start() methods also supported modifying that via their "params" parameter. Only the runqemu() wrapper function lacked a way to specify additional parameters.

[OE-core] [PATCH v2 3/4] oeqa: allow customizing image used by runqemu()

runqemu() takes all parameters for the virtual machine from the variables of the given recipe. By allowing the caller to provide a hash with variables that get applied locally, the caller gets more control. Here's the intended usage: overrides = { 'DEPLOY_DIR_IMAGE': self.resultdir

[OE-core] [PATCH v2 1/4] qemurunner: configurable timeout for run_serial()

Some commands might need to run longer than the default timeout of five seconds. If that occurred, run_serial() returned with a status code of zero (sic!) and no other indication of what went wrong. Now the timeout is configurable (with five still the default) and an explicit warning ("<<< run_ser

[OE-core] [PATCH v2 4/4] oeqa: allow persistent image writes in runqemu()

By default, runqemu() avoids modifying the image files that it boots into by enabling the qemu snapshot mode. However, some tests may want to test changes that must persists across reboots, so this mode should be optional. This can be combined by copying the image file to a temporary location firs

[OE-core] [PATCH v2 0/4] oeqa: more control over qemu

I'm currently working on testing an installer image. During that test I need to: - boot with two drives attached to the virtual machine (installer image and internal disk) - install to internal disk - reboot with just the internal disk There were several problems doing that: - attaching second d

Re: [OE-core] [PATCH 0/4 V2] runqemu: add selftest

On Fri, 2017-03-24 at 01:44 -0700, Robert Yang wrote: > * V2 > Add Qi's patch to fix hang of "oe-selftest -r wic.Wic.test_qemu_efi". The test seems to be run correctly now: runqemu - INFO - Running .../core-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-x86_64 -device virtio-ne

[OE-core] [PATCH 2/2] scripts/contrib: scripts that updates kernel templates

From: Leonardo Sandoval Updating the kernel templates (those use by the yocto-bsp script) is a mechanical process (and prone to errors) which consists of copying latest kernel template then applying string replacements from old to new kernel version. This script collects these commands allowin

[OE-core] [PATCH 1/2] scripts/lib/bsp/substrate: kernel templates for 4.10

From: Leonardo Sandoval New set of templates that target the 4.10 kernel version. [YOCTO #11174] Signed-off-by: Leonardo Sandoval --- .../arm/recipes-kernel/linux/kernel-list.noinstall | 4 +- .../linux/linux-yocto-tiny_4.10.bbappend | 33 .../recipes-kernel/linux/linu

[OE-core] [PATCHv2] dnf: move the entire dnf/rpm4 stack to Python 3

[YOCTO #11180] Signed-off-by: Alexander Kanavin --- meta/classes/rootfs_rpm.bbclass| 4 +- meta/conf/distro/include/security_flags.inc| 3 +- .../createrepo-c/createrepo-c_git.bb | 4 +- .../dnf/dnf/0028-Use-backports.lzma-not-lzma.patch | 30 --

Re: [OE-core] [PATCH] dnf: move the entire dnf/rpm4 stack to Python 3

On 03/24/2017 10:12 PM, Burton, Ross wrote: ...ython-pygpgme_0.3.bb => python3-pygpgme_0.3.bb } | 6 +- For some reason this didn't build here. | x86_64-poky-linux-gcc -m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2

[OE-core] [PATCH v2 1/2] runqemu: Automatically add a TFTP directory for slirp boot

When booting QEMU with slirp networking we want to use QEMUs TFTP server to make the images in deploy accessible to the guest. Signed-off-by: Alistair Francis --- scripts/runqemu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/runqemu b/scripts/runqemu index 23c9efb..

[OE-core] [PATCH v2 2/2] runqemu: Add a background command option

This allows callers to specify commands that should be run in the background while running QEMU. This can be specified by assigning the commands to the 'QB_BACKGROUND_COMMAND' varialbe in the machine conf. This is useful for starting automated debugging instances, automated testing instances (usin

Re: [OE-core] [PATCH] dnf: move the entire dnf/rpm4 stack to Python 3

On 24 March 2017 at 16:37, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > ...ython-pygpgme_0.3.bb => python3-pygpgme_0.3.bb} | 6 +- > For some reason this didn't build here. | x86_64-poky-linux-gcc -m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2 --sysroot=/data/poky-ma

[OE-core] ✗ patchtest: failure for "runqemu: Automatically add a T..." and 1 more

== Series Details == Series: "runqemu: Automatically add a T..." and 1 more Revision: 1 URL : https://patchwork.openembedded.org/series/5965/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been e

[OE-core] [PATCH 2/2] runqemu: Add a background command option

This allows callers to specify commands that should be run in the background while running QEMU. This can be specified by assigning the commands to the 'QB_BACKGROUND_COMMAND' varialbe in the machine conf. This is useful for starting automated debugging instances, automated testing instances (usin

[OE-core] ✗ patchtest: failure for libjpeg-turbo fails to build for aarch64/arm targets on aarch64 host

== Series Details == Series: libjpeg-turbo fails to build for aarch64/arm targets on aarch64 host Revision: 1 URL : https://patchwork.openembedded.org/series/5967/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Sev

[OE-core] [OE-Core][PATCH] libjpeg-turbo fails to build for aarch64/arm targets on aarch64 host

This is already filed in the appropriate bugzilla:    https://bugzilla.yoctoproject.org/show_bug.cgi?id=11240 Just notifying the list as the custom goes... libjpeg-turbo in recipes-graphics has an unconditional dependency on nasm-native, which is intel specific and wont be provided on non intel a

Re: [OE-core] [PATCH] openssl: Fix build with thumb2

Yeah they are essentially same On Fri, Mar 24, 2017 at 9:50 AM Burton, Ross wrote: > > On 24 March 2017 at 16:40, Khem Raj wrote: > > create mode 100644 pull-30041/-cover-letter.patch > create mode 100644 > pull-30041/0001-db-Fix-atomic-function-namespace-clash-with-clang-bu.patch > cre

[OE-core] [PATCH 4/4] oeqa: allow persistent image writes in runqemu()

By default, runqemu() avoids modifying the image files that it boots into by enabling the qemu snapshot mode. However, some tests may want to test changes that must persists across reboots, so this mode should be optional. This can be combined by copying the image file to a temporary location firs

[OE-core] [PATCH 0/4] oeqa: more control over qemu

I'm currently working on testing an installer image. During that test I need to: - boot with two drives attached to the virtual machine (installer image and internal disk) - install to internal disk - reboot with just the internal disk There were several problems doing that: - attaching second d

[OE-core] [PATCH 2/4] oeqa: allow extending qemuparams="..."

Sometimes it is useful to reconfigure the qemu virtual machine directly. runqemu has the "qemuparams" parameter for that, and the underlying start() methods also supported modifying that via their "params" parameter. Only the runqemu() wrapper function lacked a way to specify additional parameters.

[OE-core] [PATCH 3/4] oeqa: allow customizing image used by runqemu()

runqemu() takes all parameters for the virtual machine from the variables of the given recipe. By allowing the caller to provide a hash with variables that get applied locally, the caller gets more control. Here's the intended usage: overrides = { 'DEPLOY_DIR_IMAGE': self.resultdir

[OE-core] [PATCH 1/4] qemurunner: configurable timeout for run_serial()

Some commands might need to run longer than the default timeout of five seconds. If that occurred, run_serial() returned with a status code of zero (sic!) and no other indication of what went wrong. Now the timeout is configurable (with five still the default) and an explicit warning ("<<< run_ser

[OE-core] ✗ patchtest: failure for openssl: Fix build with thumb2

== Series Details == Series: openssl: Fix build with thumb2 Revision: 1 URL : https://patchwork.openembedded.org/series/5964/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the p

Re: [OE-core] [PATCH] openssl: Fix regression when building for thumb2

On Fri, Mar 24, 2017 at 8:01 AM, Max Krummenacher wrote: > Commit 'c8da8ce openssl: Fix build with clang' introduced a regression. > do_compile fails when building with gcc/thumb2. > > Note that I did not test if it still builds with clang. > > Prevents the following when building with thumb2: >

[OE-core] [PATCH 1/2] runqemu: Automatically add a TFTP directory for slirp boot

When booting QEMU with slirp networking we want to use QEMUs TFTP server to make the images in deploy accessible to the guest. Signed-off-by: Alistair Francis --- scripts/runqemu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/runqemu b/scripts/runqemu index 23c9efb..

Re: [OE-core] [PATCH] openssl: Fix build with thumb2

On 24 March 2017 at 16:40, Khem Raj wrote: > create mode 100644 pull-30041/-cover-letter.patch > create mode 100644 pull-30041/0001-db-Fix-atomic- > function-namespace-clash-with-clang-bu.patch > create mode 100644 pull-30041/0002-libvorbis- > Contain-gcc-specific-compiler-flags-using-.pat

[OE-core] [PATCH] openssl: Fix build with thumb2

Signed-off-by: Khem Raj --- ...build-with-clang-using-external-assembler.patch | 18 ++-- pull-30041/-cover-letter.patch | 32 ...ic-function-namespace-clash-with-clang-bu.patch | 84 +++ ...ontain-gcc-specific-compiler-flags-using-.patch | 96

[OE-core] [PATCH] dnf: move the entire dnf/rpm4 stack to Python 3

[YOCTO #11180] Signed-off-by: Alexander Kanavin --- meta/classes/rootfs_rpm.bbclass| 4 +- .../createrepo-c/createrepo-c_git.bb | 4 +- .../dnf/dnf/0028-Use-backports.lzma-not-lzma.patch | 30 -- .../dnf/0030-Run-python-scripts-using-env.patch| 6 +-

Re: [OE-core] Remove do_install_append() from zsh's recipe

On Fri, Mar 24, 2017 at 9:28 AM, Burton, Ross wrote: > Patches for meta-oe need to go to the > openembedded-de...@lists.openembedded.org list, not -core which is specific > to oe-core. > > Also put [meta-oe] in the subject prefix, and send the patch using > git-format-patch with a properly formatt

[OE-core] [PATCH] boost: various cleanups

Re-order some assignments to be logically arranged. Remove the set -ex statements as they serve no purpose. Pass --debug-configuration to see what configuration steps boost is taking. Signed-off-by: Ross Burton --- meta/recipes-support/boost/boost.inc | 10 -- 1 file changed, 4 inserti

[OE-core] [PATCH] boost: port boost-python to Python 3

As Python 3 is the default Python version, change Boost to build against Python 3 instead of Python 2 if enabled. It's not simple to support both, so this means that support for building boost-python against Python 2 has been removed. This involves backporting a number of patches upstream to fix

[OE-core] [PATCH 1/2] tzcode: update to 2017b

From: Armin Kuster Briefly: Haiti has resumed DST. Changes to past and future time stamps Haiti resumed observance of DST in 2017. (Thanks to Steffen Thorsen.) Changes to past time stamps Liberia changed from -004430 to +00 on 1972-01-07, not 1972-05-01. Use "MMT" to abbrev

[OE-core] [PATCH 2/2] tzdata: update to 2017b

From: Armin Kuster Signed-off-by: Armin Kuster --- meta/recipes-extended/tzdata/{tzdata_2017a.bb => tzdata_2017b.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/tzdata/{tzdata_2017a.bb => tzdata_2017b.bb} (98%) diff --git a/meta/recipes-extended/tzda

Re: [OE-core] Using MACHINE_FEATURES in a native recipe

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > Richard Purdie > Sent: den 23 mars 2017 17:43 > To: Andre McCurdy; OE Core mailing list > Subject: Re: [OE-core] Using MACHINE_FEATURES in

[OE-core] [PATCH] openssl: Fix regression when building for thumb2

Commit 'c8da8ce openssl: Fix build with clang' introduced a regression. do_compile fails when building with gcc/thumb2. Note that I did not test if it still builds with clang. Prevents the following when building with thumb2: | ghash-armv4.S: Assembler messages: | ghash-armv4.S:88: Error: thumb

Re: [OE-core] [PATCH 0/2] fix valgrind ptest

Hi Ross, Will update and send it soon. Regards, Maxin From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Friday, March 24, 2017 4:54 PM To: John, Maxin Cc: OE-core Subject: Re: [OE-core] [PATCH 0/2] fix valgrind ptest On 24 March 2017 at 14:52, Maxin B. John mailto:maxin.j...@intel.com

[OE-core] [PATCH 2/2] valgrind: correct the comparison logic in vg_regtest

do_diffs in the vg_regtest script compares the actual test output against the expected test output and returns 0 if it matches. Previous upgrade modified the return value of do_diffs() and that resulted in ptest failures. [YOCTO #8471] Signed-off-by: Maxin B. John --- .../0005-Modify-vg_test-w

[OE-core] [PATCH 0/2] fix valgrind ptest

Updated perl path in vg_regtest (test script) Fixed the .exp and .out comparison logic [YOCTO #8471] Maxin B. John (2): valgrind: vg_regtest.in: fix perl script valgrind: correct the comparison logic in vg_regtest ...-vg_test-wrapper-to-support-PTEST-formats.patch | 4 +-- .../valgrind/val

[OE-core] [PATCH 1/2] valgrind: vg_regtest.in: fix perl script

@PERL@ in vg_regtest.in causes recipe specific sysroot based perl to be present in the vg_regtest script, making it unusable in the target. Use /usr/bin/perl instead of @PERL@ to fix it. Signed-off-by: Maxin B. John --- .../valgrind/valgrind/fixed-perl-path.patch| 33 +++

Re: [OE-core] [PATCH 0/2] fix valgrind ptest

On 24 March 2017 at 14:52, Maxin B. John wrote: > Maxin B. John (2): > vg_regtest.in : fix perl script > do_diffs: correct the comparison logic > Both patches missing the valgrind: prefix. Ross -- ___ Openembedded-core mailing list Openembedded-c

[OE-core] [PATCH 1/2] vg_regtest.in : fix perl script

@PERL@ in vg_regtest.in causes recipe specific sysroot based perl to be present in the vg_regtest script, making it unusable in the target. Use /usr/bin/perl instead of @PERL@ to fix it. Signed-off-by: Maxin B. John --- .../valgrind/valgrind/fixed-perl-path.patch| 33 +++

[OE-core] [PATCH 2/2] do_diffs: correct the comparison logic

do_diffs in the vg_regtest script compares the actual test output against the expected test output and returns 0 if it matches. Previous upgrade modified the return value of do_diffs() and that resulted in ptest failures. [YOCTO #8471] Signed-off-by: Maxin B. John --- .../0005-Modify-vg_test-w

[OE-core] [PATCH 0/2] fix valgrind ptest

Updated perl path in vg_regtest (test script) Fixed the .exp and .out comparison logic [YOCTO #8471] Maxin B. John (2): vg_regtest.in : fix perl script do_diffs: correct the comparison logic ...-vg_test-wrapper-to-support-PTEST-formats.patch | 4 +-- .../valgrind/valgrind/fixed-perl-path.p

[OE-core] [PATCH 2/2] oeqa.buildperf: limit the length of error output

Limit the length of error logs to 40 lines. We don't need to show/archive thousands of lines of bitbake logs if an error occurs. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/buildperf/base.py

[OE-core] [PATCH 1/2] oeqa.utils.commands: limit runCmd exception output

Make it possible to limit the length of output lines shown in runCmd exceptions. E.g when running bitbake we easily get thousands of lines of log output, where only the last few (tens) are interesting or relevant when an error occurs. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/comman

Re: [OE-core] Remove do_install_append() from zsh's recipe

Hi, On 24 March 2017 at 14:07, Cody Piersall wrote: > This is my first post to this list, so please feel free to correct me > on any etiquette issues I've messed up. > Patches for meta-oe need to go to the openembedded-de...@lists.openembedded.org list, not -core which is specific to oe-core.

[OE-core] [PATCH 1/6] oe-build-perf-test: pack all buildstat in one file

Write out all buildstats into one big json file, instead of using multiple per-measurement files. Individual buildstats will be indexed using "." as the key. Also, changes the per-testcase working directories into temporary directories that will be removed after test execution as there are no more

[OE-core] [PATCH 0/6] oe-build-perf-test: re-organize buildstats archiving

This patchset optimizes the way buildstats are stored in oe-build-perf-test result data. After this change buildstats are stored under refs/notes/buildstats/* in Git, and thus, they're not cloned/fetched by default. The motivation is to reduce the data footprint as buildstats are rarely used but th

[OE-core] [PATCH 5/6] scripts/oe-git-archive: implement --notes

Option for adding git-notes to the commit. [YOCTO #10582] Signed-off-by: Markus Lehtonen --- scripts/oe-git-archive | 21 ++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/scripts/oe-git-archive b/scripts/oe-git-archive index 1805ab3..ab19cb9 100755 --- a/scri

[OE-core] [PATCH 6/6] build-perf-test-wrapper.sh: store buildstats under git-notes

In order to dramatically reduce the data footprint of the result branches. This makes cloning/pulling result repositories a lot faster. Buildstats can still be accessed, when needed by doing git fetch refs/notes/buildstats/*:refs/notes/buildstats/* [YOCTO #10582] Signed-off-by: Markus Lehtonen -

[OE-core] [PATCH 2/6] oe-build-perf-test: sum rusage in buildstats

Instead of separate rusage and child rusage values, only store their sum value in buildstats. This is a big reduction in data footprint without really losing any interesting data. Also, utilize OrderedDict to order data more logically. [YOCTO #10582] Signed-off-by: Markus Lehtonen --- meta/lib

[OE-core] [PATCH 4/6] scripts/oe-git-archive: implement --exclude

May be used for excluding certain files from the commit. [YOCTO #10582] Signed-off-by: Markus Lehtonen --- scripts/oe-git-archive | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/scripts/oe-git-archive b/scripts/oe-git-archive index aef4ba1..1805ab3 100755 --- a

[OE-core] [PATCH 3/6] scripts/oe-git-archive: fix pushing

Git arguments were badly laid out. Signed-off-by: Markus Lehtonen --- scripts/oe-git-archive | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/scripts/oe-git-archive b/scripts/oe-git-archive index 117118b..aef4ba1 100755 --- a/scripts/oe-git-archive +++ b/scripts/oe-git-ar

[OE-core] Remove do_install_append() from zsh's recipe

Hello, The recipe for building zsh includes the following function: do_install_append () { rm -fr ${D}/usr/share } For me, this is not a useful function because zsh store lots of nice functionality in the "/usr/share/zsh/5.0.5/functions" directory. This includes things like typing cd and a

Re: [OE-core] [PATCH] image_types: perform fsck on created ext image

On 24 March 2017 at 14:01, Enrico Joerns wrote: > But, there is another difference between our patches. We use `-pvfD`, > while you use `-fy` as an fsck.extN option. > Indeed, I've selected your patch for my staging branch. Cheers, Ross -- ___ Openem

Re: [OE-core] [PATCH] image_types: perform fsck on created ext image

Hi Daniel, On 03/24/2017 02:34 PM, Daniel Schultz wrote: Hi Enrico, I have sent fixes for the same problem on Monday. These include a fix of the wrong return code after optimizations (now it returns 0) and an fsck execution after the creation of EXT partitions. The patch which is identical to

Re: [OE-core] design question: should layer.conf contain "PREFERRED_VERSION" settings?

On 22 March 2017 at 16:32, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > Someone needs to file a bug... > Found https://bugzilla.yoctoproject.org/show_bug.cgi?id=8745. Currently a future enhancement, I think we should reschedule this to 2.4. Simply bailing shouldn't be that much

Re: [OE-core] [PATCH] image_types: perform fsck on created ext image

On 24 March 2017 at 13:34, Daniel Schultz wrote: > The patch which is identical to yours wasn't applied so far, the other > ones were. > Whoops, that was marked locally as merged but wasn't in the tree. Now it's staged. Ross -- ___ Openembedded-core

Re: [OE-core] [PATCH] image_types: perform fsck on created ext image

Hi Enrico, I have sent fixes for the same problem on Monday. These include a fix of the wrong return code after optimizations (now it returns 0) and an fsck execution after the creation of EXT partitions. The patch which is identical to yours wasn't applied so far, the other ones were. -- M

[OE-core] [PATCH] wic: use kernel_dir to find systemd-efi bootloader

Fixed test failure caused by using bootimg_dir path instead of kernel_dir to find systemd-efi bootloader: FAIL: test_systemd_bootdisk (oeqa.selftest.wic.Wic) ... FileNotFoundError: [Errno 2] No such file or directory: 'tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot/usr/shar

Re: [OE-core] [PATCH 3/3] apt: fix hardcode of /usr/lib

On 24 March 2017 at 08:55, Robert Yang wrote: > - install -m 0644 ${S}/debian/apt.systemd.daily ${D}/usr/lib/apt/ > + install -m 0644 ${S}/debian/apt.systemd.daily ${D}${libdir}/apt/ > $ grep -r apt.systemd.daily debian/apt-daily.service:ExecStart=/usr/lib/apt/apt.systemd.daily debia

[OE-core] [PATCH] image_types: perform fsck on created ext image

When performing a file system check, the image created with mkfs will trigger Pass 3A ('Optimizing directories') which turns the file system into state "changed" (EXT2_FLAG_CHANGED). This will let fsck request a reboot by setting the return code flag "2". The result of this is that each ext-image

[OE-core] [PATCH] mdadm: update criteria to build with corosync

From: Kai Kang mdadm only works with corosync 2.x which provides header file corosync/cmap.h. If build mdadm with corosync 1.x, it fails with: | member.c:12:27: fatal error: corosync/cmap.h: No such file or directory | #include |^ Build with corosync only header fi

[OE-core] [PATCH 1/3] runtime-test.py: fix typo

roofs -> rootfs. Signed-off-by: Robert Yang --- meta/lib/oeqa/selftest/runtime-test.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/lib/oeqa/selftest/runtime-test.py b/meta/lib/oeqa/selftest/runtime-test.py index 171a373..ea31c18 100644 --- a/meta/lib/oeqa/selfte

[OE-core] [PATCH 3/3] apt: fix hardcode of /usr/lib

It should be ${libdir} rather than /usr/lib, otherwise it would fail when multilib. Signed-off-by: Robert Yang --- meta/recipes-devtools/apt/apt-package.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/apt/apt-package.inc b/meta/recipes-devtools/apt/

[OE-core] [PATCH 2/3] scripts/wic: fix typo

roofs -> rootfs Signed-off-by: Robert Yang --- scripts/wic | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/wic b/scripts/wic index 8e9c05c..a5f2dbf 100755 --- a/scripts/wic +++ b/scripts/wic @@ -146,7 +146,7 @@ def wic_create_subcommand(args, usage_str):

[OE-core] [PATCH 0/3] meta: 3 minor fixes

The following changes since commit 3b5ac72bdf76ac8ff98dc3c882a4edc77c6e2c33: rpm: add a "rpm-build" PROVIDES (2017-03-22 15:09:26 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/3fixes http://cgit.openembedded.org/openembedded-core-co

[OE-core] [PATCH v2] logrotate: Add systemd support

Currently, this recipe only supports daily scheduling via a cron job. This commit adds support for systemd, including systemd service and systemd timer. When the corresponding distro feature is enabled the systemd variant will be used. The timer granularity and its accuracy are also configurable.

[OE-core] [PATCH 1/4] oeqa/targetcontrol.py: modify it to test runqemu

Modify the following files to test runqemu: targetcontrol.py utils/commands.py utils/qemurunner.py We need simulate how "runqemu" works in command line, so when test "runqemu", the targetcontrol.py, utils/commands.py and utils/qemurunner.py don't have to find the rootfs or set env vars

[OE-core] [PATCH 4/4] targetcontrol.py: use logger.info to replace of bb.note

The bb.note prints multiple same lines when invoke this class again, but if we set mainlogger.propagate = False, nothing would be printed, according to logging's document: https://docs.python.org/3/library/logging.html Note If you attach a handler to a logger and one or more of its ancestors, it m

[OE-core] [PATCH 3/4] selftest/runqemu.py: add it to test runqemu

Usage: $ oe-selftest -r runqemu Current test cases: $ runqemu nographic qemux86-64 $ runqemu nographic qemux86-64 ext4 $ runqemu nographic qemux86-64 iso $ runqemu nographic core-image-minimal $ runqemu nographic core-image-minimal vmdk $ runqemu nographic core-image-minimal vdi $ runqemu nographi

[OE-core] [PATCH 0/4 V2] runqemu: add selftest

* V2 Add Qi's patch to fix hang of "oe-selftest -r wic.Wic.test_qemu_efi". // Robert The following changes since commit 3b5ac72bdf76ac8ff98dc3c882a4edc77c6e2c33: rpm: add a "rpm-build" PROVIDES (2017-03-22 15:09:26 +) are available in the git repository at: git://git.openembedded.org

[OE-core] [PATCH 2/4] qemurunner.py: fix handling of runqemuparams

From: Chen Qi The launch() doesn't need runqemuparams, we need handle it in start(). Signed-off-by: Chen Qi Signed-off-by: Robert Yang --- meta/lib/oeqa/utils/qemurunner.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/lib/oeqa/utils/qemurunner.py b/meta/lib/

[OE-core] [PATCH 1/2] srctree.bbclass: Download sourcecode and make it searchable

This class is used to create a symlink to the source in ${S} in a separate directory structure. ${SECTION} is used, if available, for naming the path. Intended for 'devtool srctree ' to set up a tree with the source for all specified recipes and their dependencies to be able to do a more convenien

[OE-core] [PATCH 0/2] Make source code browsable locally

In our organization, there is a demand to be able download source code for searching. With the use of sstate-cache this has been challenge. Also, the source is not gathered but rather spread in a larger directory structure together with build output. There are probably others that also want to b

[OE-core] [PATCH 2/2] devtool: srctree: New command for setting up browsable source-code

Setup a directory tree for source code according to section name. (if known). This tree is intended for code browsing ONLY. If source is moved, for instance with devtool modify, this command should be rerun to be up-to-date with that move. Signed-off-by: Tobias Hagelborn --- scripts/lib/devtool