[OE-core] ✗ patchtest: failure for f2fs-tools: Update to Version 1.8.0

== Series Details == Series: f2fs-tools: Update to Version 1.8.0 Revision: 1 URL : https://patchwork.openembedded.org/series/6013/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on

[OE-core] [PATCH] f2fs-tools: Update to Version 1.8.0

Signed-off-by: Yong, Jonathan --- .../0002-Fix-mkfs-out-of-tree-builds.patch | 27 ++ .../{f2fs-tools_1.4.0.bb => f2fs-tools_1.8.0.bb} | 5 ++-- 2 files changed, 30 insertions(+), 2 deletions(-) create mode 100644

[OE-core] [PATCH] f2f2-tools 1.4.0 -> 1.8.0

Upgrade f2fs-tools, now supports encryption. Yong, Jonathan (1): f2fs-tools: Update to Version 1.8.0 .../0002-Fix-mkfs-out-of-tree-builds.patch | 27 ++ .../{f2fs-tools_1.4.0.bb => f2fs-tools_1.8.0.bb} | 5 ++-- 2 files changed, 30 insertions(+), 2 deletions(-)

[OE-core] [PATCH] f2fs-tools: Update to Version 1.8.0

Signed-off-by: Yong, Jonathan --- .../0002-Fix-mkfs-out-of-tree-builds.patch | 27 ++ .../{f2fs-tools_1.4.0.bb => f2fs-tools_1.8.0.bb} | 5 ++-- 2 files changed, 30 insertions(+), 2 deletions(-) create mode 100644

[OE-core] [PATCH] bitbake.conf: sort HOSTTOOLS and remove duplicates

Cleanup only, no functional changes. Signed-off-by: Andre McCurdy --- meta/conf/bitbake.conf | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index fa5445b..96a9ed9 100644 ---

[OE-core] [PATCH 1/1] apt: fix libdir path for apt.systemd.daily

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

[OE-core] [PATCH 0/1 V2] apt: fix libdir path for apt.systemd.daily

* V2 Also fix apt-daily.service and apt.apt-compat.cron.daily as Ross commented. // Robert The following changes since commit 9c948d3de08f158387e08a17cdc0cedc7d26bb54: oeqa/selftest: don't use cleanall in selftests (2017-03-27 20:22:43 +0100) are available in the git repository at:

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

On 03/27/2017 09:26 PM, Richard Purdie wrote: On Mon, 2017-03-27 at 03:34 -0700, Robert Yang wrote: Fixed: $ bitbake meta-ide-support $ . ./tmp/environment-setup-i586-poky-linux $ runqemu tmp/deploy/images/qemux86/core-image-sato- qemux86.qemuboot.conf [snip] /bin/sh: sudo: command not found

Re: [OE-core] [PATCH v2] eudev: restore userspace firmware loading support

Hi Otavio, On 28 March 2017 at 07:09, Otavio Salvador wrote: > From: Lauren Post > > This sycncs eudev with systemd. This is required for old kernels to > work and does same backport as did in: > > , > | commit

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

Hi Alex, On Tuesday, 28 March 2017 1:53:59 AM NZDT Alexander Kanavin wrote: > [YOCTO #11180] > > Signed-off-by: Alexander Kanavin > --- If you're doing another rev can you please have a reasonable commit message in here? Even if it's trivial. Thanks, Paul

[OE-core] [morty][PATCH] parselogs: Whitelist NUC6 firmware load error message on genericx86-64

This was already whitelisted, but the 4.8 kernel changed the error message, causing it to get caught by parselogs again. Fixes [YOCTO #10494]. Signed-off-by: California Sullivan Signed-off-by: Ross Burton (cherry picked from commit

[OE-core] [PATCH v2] eudev: restore userspace firmware loading support

From: Lauren Post This sycncs eudev with systemd. This is required for old kernels to work and does same backport as did in: , | commit 31163abc7bedd477c1aad10e6d1f47dbee194513 | Author: Jonathan Liu | Date: Thu Mar 19 15:38:32 2015 +1100 | |

[OE-core] [PATCHv2 1/1] oeqa/core/loader.py: Do not import underscore modules by default

From: Mariano Lopez Underscore modules are meant to be run only when manually added to the test suite, so far another mechanisms are in place to make this happen with runtime, sdk, and esdk (mostly in test* bbclasses). This will add such functionality in the core

[OE-core] ✗ patchtest: failure for eudev: restore userspace firmware loading support

== Series Details == Series: eudev: restore userspace firmware loading support Revision: 1 URL : https://patchwork.openembedded.org/series/6004/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have

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

By default, QemuRunner 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

[OE-core] [PATCH v4 2/3] 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':

[OE-core] [PATCH v4 1/3] 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

[OE-core] [PATCH v4 0/3] 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

[OE-core] [PATCH] eudev: restore userspace firmware loading support

From: Lauren Post This sycncs eudev with systemd. This is required for old kernels to work and does same backport as did in: , | commit 31163abc7bedd477c1aad10e6d1f47dbee194513 | Author: Jonathan Liu | Date: Thu Mar 19 15:38:32 2015 +1100 | |

[OE-core] OpenEmbedded Developer Meeting Oct 22 in Prague

We've had some discussion for scheduling the next OEDEM around the ELCE in Prague. The Yocto Project Developer day is the Thursday after the conference (as is the kernel summit). To avoid conflicting with them the OpenEmbedded board proposes holding the meeting Sunday before ELCE in Prague. That

[OE-core] ✗ patchtest: failure for oeqa/core/loader.py: Do not import underscore modules by default

== Series Details == Series: oeqa/core/loader.py: Do not import underscore modules by default Revision: 1 URL : https://patchwork.openembedded.org/series/6002/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response.

[OE-core] [PATCH 1/1] oeqa/core/loader.py: Do not import underscore modules by default

From: Mariano Lopez Underscore modules are meant to be run only when manually added to the test suite, so far another mechanisms are in place to make this happen with runtime, sdk, and esdk (mostly in test* bbclasses). This will add such functionality in the core

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

On Mon, Mar 27, 2017 at 11:14 AM, Burton, Ross wrote: > > On 27 March 2017 at 16:10, Trevor Woerner wrote: >> >> What I want is to get rid of the mouse pointer completely. Formfactor has >> variables that would appear to affect things like rotation and

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

On Mon, Mar 27, 2017 at 04:52:33PM +0100, Burton, Ross wrote: > On 27 March 2017 at 16:47, Denys Dmytriyenko wrote: > > > I haven't personally tested 2017.03 yet, as we are staying on 2017.01 for a > > bit longer... > > > > It that just because you've stabilised, or is there

[OE-core] [PATCH] insane.bbclass: error if file-rdeps not met

Missing runtime dependencies should result in an error rather than a warning. Indeed, if RPM is listed in PACKAGE_CLASSES, it will throw an error rather than install packages with missing dependencies. This functionality should be consistent across package types. This patch ensures that an error

[OE-core] [PATCH] devtool: open kconfig fragment in binary mode

When devtool writes to the kconfig fragment, it writes the output of the diff command returned from pipe.communicate(). This function returns binary objects. We should open the kconfig fragment file in binary mode if we expect to write binary objects to it. [YOCTO #11171] Signed-off-by: Stephano

[OE-core] [PATCH] scripts/yocto-compat-layer.py: Add dependency validation in add_layer

Some layers don't have dependencies so add a validation to avoid exception when trying to None.split(). Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

Re: [OE-core] CPU profiling at thread level

On Sat, 2017-03-25 at 21:44 +0530, Munagala Naresh wrote: > Hi Team, > > To analyzes the CPU load consumption of a particular process, we need > to find the thread level consumption. Default top and ps utils are > not supporting all the parameters that are available in > Linux/Android.  > >

Re: [OE-core] CPU profiling at thread level

On Sat, 2017-03-25 at 21:44 +0530, Munagala Naresh wrote: > Hi Team, > > > > To analyzes the CPU load consumption of a particular process, we need > to find the thread level consumption. Default top and ps utils are not > supporting all the parameters that are available in Linux/Android. > I

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

On Mon, Mar 27, 2017 at 02:19:56PM +0100, Burton, Ross wrote: > On 26 March 2017 at 22:14, Denys Dmytriyenko wrote: > > > At least 2 typos in the description... > > > > Typos aside, this is past the M3 deadline but RC2 is running late, is there > a good reason to have the

[OE-core] [PATCH 2/2] boost: enable more libraries

Enable the fiber, metaparse, and type_erasure libraries. We can't enable coroutine2 as it needs C++11 and it appears our hacks to configure the compiler mean boost doesn't think we support that. Signed-off-by: Ross Burton --- meta/recipes-support/boost/boost.inc | 5

[OE-core] [PATCH 1/2] boost: build context and coroutine on ARM

With the right flags to the build, the context library can be built on ARM. [ YOCTO #11253 ] Signed-off-by: Ross Burton --- meta/recipes-support/boost/boost.inc | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git

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

On 27/03/17 07:38, Richard Purdie wrote: > On Fri, 2017-03-24 at 15:06 -0700, mariano.lo...@linux.intel.com wrote: >> From: Mariano Lopez >> >> This series allows to import custom targets to be used with runtime >> testing. >> Now is possible to have a target in

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

On 27 March 2017 at 16:10, Trevor Woerner wrote: > What I want is to get rid of the mouse pointer completely. Formfactor has > variables that would appear to affect things like rotation and whether or > not > the calibration routine gets called when X starts up. I don't see

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

On Mon 2017-03-27 @ 12:35:51 PM, Burton, Ross wrote: > On 25 March 2017 at 05:19, Trevor Woerner wrote: > > > 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. > > > >

[OE-core] Yocto Project Status WW13’17

Current Dev Position: YP 2.3 M4 Next Deadline: YP 2.3 M4 Cutoff is April 10, 2017 *** FEATURE FREEZE for 2.3 is now in effect. *** SWAT team rotation: Jussi -> Stephano on Mar. 24, 2017. SWAT team rotation: Stephano -> Maxin on Mar. 31, 2017.

[OE-core] [PATCH] u-boot: Update to 2017.03 release

Upgrade U-Boot to the latest version. Signed-off-by: Marek Vasut Cc: Denys Dmytriyenko Cc: Richard Purdie Cc: Ross Burton --- .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2

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

On Mon, 2017-03-27 at 15:19 +0300, Alexander Kanavin wrote: > On 03/25/2017 07:56 PM, Richard Purdie wrote: > > > > > > > > [YOCTO #11180] > > So close but: > > > > https://autobuilder.yocto.io/builders/nightly-multilib/builds/226 > > https://autobuilder.yocto.io/builders/nightly-x32/builds/206

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

On Fri, 2017-03-24 at 15:06 -0700, mariano.lo...@linux.intel.com wrote: > 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

Re: [OE-core] [PATCH] classes: Replace "if test" file tests with POSIX file tests

On Sat, 2017-03-25 at 14:03 -0400, Robert P. J. Day wrote: > In entire meta/classes/ directory, replace shell tests of the form > "if test -? ..." with POSIX tests of the form "if [ -? ... > > Signed-off-by: Robert P. J. Day > > --- > >   as i cannot abide those silly

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

On Mon, Mar 27, 2017 at 10:19 AM, Burton, Ross wrote: ... > Also what boards has it been tested on? As it's from Otavio I presume the > Freescale boards have been tested. Denys, have you tested this version on > your boards? We are using it internally and we will upgrade

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

On 27 March 2017 at 14:26, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > sudo is already in HOSTTOOLS_NONFATAL? > Good point well made. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

On Mon, 2017-03-27 at 03:34 -0700, Robert Yang wrote: > Fixed: > $ bitbake meta-ide-support > $ . ./tmp/environment-setup-i586-poky-linux > $ runqemu tmp/deploy/images/qemux86/core-image-sato- > qemux86.qemuboot.conf > > [snip] > /bin/sh: sudo: command not found > runqemu - ERROR - Failed to

[OE-core] [PATCHv4 2/2] 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 +-

[OE-core] [PATCHv4 1/2] python3: do not hardcode "lib" into site-packages search path

This was not working in multilib or x32 setups and amazingly, was not noticed until now. The actual modification is in Lib/site.py, the rest is just devtool moving things around in the patch. Signed-off-by: Alexander Kanavin ---

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

On 26 March 2017 at 22:14, Denys Dmytriyenko wrote: > At least 2 typos in the description... > Typos aside, this is past the M3 deadline but RC2 is running late, is there a good reason to have the upgrade in? Also what boards has it been tested on? As it's from Otavio I

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

On Sun, Mar 26, 2017 at 6:14 PM, Denys Dmytriyenko wrote: > On Sun, Mar 26, 2017 at 05:08:13PM -0300, Otavio Salvador wrote: >> Ths 2017.03 release is out since March 13th 2017 and is the latest >> stable release prior Pyro release. > > At least 2 typos in the description...

[OE-core] [PATCH v2] u-boot: Update to 2017.03 release

This 2017.03 release is out since March 13th, 2017 and is the latest stable release prior Pyro release. Signed-off-by: Otavio Salvador --- Changes in v2: - Fix typo in commit log .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 +-

Re: [OE-core] [PATCHv3 1/2] python3: do not hardcode "lib" into site-packages search path

On 03/27/2017 03:58 PM, Burton, Ross wrote: + file://0001-Do-not-hardcode-lib-into-site-packages-path.patch \ This should probably be added to meta/recipes-devtools/python/python3/python-3.3-multilib.patch instead of being in a separate patch. Sure, but the patch that does that

[OE-core] [PATCH 1/2] oeqa: tolerate interrupted select() while waiting for qemu

Sometimes, the OEQA utility code aborts with: ... File ".../meta/lib/oeqa/utils/qemurunner.py", line 131, in start return self.launch(launch_cmd, qemuparams=qemuparams, get_ip=get_ip, extra_bootparams=extra_bootparams) File ".../meta/lib/oeqa/utils/qemurunner.py", line 259, in

[OE-core] [PATCH 2/2] oeqa: QEMU_USE_KVM can list machines

Previously, QEMU_USE_KVM=True enabled the use of kvm only when "x86" was in the MACHINE name. That is too limiting, because for example intel-corei7-64 can also use kvm but it wasn't possible to enable that without changing OE-core. That traditional usage is still supported. In addition,

[OE-core] [PATCH 0/2] oeqa: runqemu enhancements

Just something that I happened to notice when using oe-selftest a bit more... Both patches are non-essential enhancements and thus can wait until after 2.4. Patrick Ohly (2): oeqa: tolerate interrupted select() while waiting for qemu oeqa: QEMU_USE_KVM can list machines

Re: [OE-core] [PATCHv3 1/2] python3: do not hardcode "lib" into site-packages search path

On 27 March 2017 at 13:53, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > +file://0001-Do-not-hardcode-lib-into-site-packages-path.patch > \ > This should probably be added to meta/recipes-devtools/python/python3/python-3.3-multilib.patch instead of being in a

[OE-core] [PATCHv3 2/2] 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 +-

[OE-core] [PATCHv3 1/2] python3: do not hardcode "lib" into site-packages search path

This was not working in multilib or x32 setups and amazingly, was not noticed until now. Signed-off-by: Alexander Kanavin --- ...-not-hardcode-lib-into-site-packages-path.patch | 33 ++ meta/recipes-devtools/python/python3_3.5.2.bb |

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

On 03/25/2017 07:56 PM, Richard Purdie wrote: [YOCTO #11180] So close but: https://autobuilder.yocto.io/builders/nightly-multilib/builds/226 https://autobuilder.yocto.io/builders/nightly-x32/builds/206 This is actually a bug in our target Python 3 installation. No idea how it went

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

On 25 March 2017 at 05:19, Trevor Woerner wrote: > 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. > This is what the touchscreen variable in the formfactor recipe is for.

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

On 27 March 2017 at 11:34, Robert Yang wrote: > [snip] > /bin/sh: sudo: command not found > runqemu - ERROR - Failed to setup tap device. Run runqemu-gen-tapdevs to > manually create. > [snip] > This only happens if the tapdevs haven't already been generated, in which

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

Hi Daniel, On 03/27/2017 09:37 AM, Daniel Schultz wrote: 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

[OE-core] [PATCH 2/2] oe-find-native-sysroot: work with RSS

The generic STAGING_DIR_NATIVE is gone since RSS, so when find OECORE_NATIVE_SYSROOT, the user has to specify which recipe's STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT. * The usage is changed from ". oe-find-native-sysroot" to ". oe-find-native-sysroot ". * The oe-run-native's

[OE-core] [PATCH 0/2] oe-find-native-sysroot: make it work with RSS

The following changes since commit 78928016f4cf38cf6751cb089200bf950d07ae93: classes: Replace "if test" file tests with POSIX file tests (2017-03-27 11:08:28 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/rssfix

[OE-core] [PATCH 1/2] oe-run-native: OLDPATH -> OLD_PATH

It's a typo. Signed-off-by: Robert Yang --- scripts/oe-run-native | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/oe-run-native b/scripts/oe-run-native index 7e26ea3fcc..f2453e705a 100755 --- a/scripts/oe-run-native +++

[OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

Fixed: $ bitbake meta-ide-support $ . ./tmp/environment-setup-i586-poky-linux $ runqemu tmp/deploy/images/qemux86/core-image-sato-qemux86.qemuboot.conf [snip] /bin/sh: sudo: command not found runqemu - ERROR - Failed to setup tap device. Run runqemu-gen-tapdevs to manually create. [snip] The

[OE-core] [PATCH 0/1] bitbake.conf: add sudo to HOSTTOOLS

The following changes since commit 78928016f4cf38cf6751cb089200bf950d07ae93: classes: Replace "if test" file tests with POSIX file tests (2017-03-27 11:08:28 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/tools

Re: [OE-core] another cleanup: "grep ... >/dev/null" -> "grep -q"?

On 25 March 2017 at 19:22, Robert P. J. Day wrote: > 1) can most of those be simplified with "grep -q"? > Yes. > 2) is there any need for "egrep" in that last match? > egrep is grep -E, but that regex is a valid basic RE, so that can just be grep. Ross --

[OE-core] [PATCH] oeqa/selftest: don't use cleanall in selftests

* devtool: oeqa.selftest.devtool.DevtoolTests is taking 4 or more hours on the autobuilder because the cleanall call deletes the tarball of the kernel source, forcing a large clone which is especially long on an NFS mount. The cleanall invocation isn't really required here and switching to

[OE-core] [PATCH v3 2/3] 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':

[OE-core] [PATCH v3 1/3] 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

[OE-core] [PATCH v3 0/3] 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

[OE-core] [PATCH v3 3/3] 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

[OE-core] [PATCH 0/1] rpm: change PROVIDES rpm-build to RPROVIDES

The following changes since commit b2a785f19fe25d244179b8672c846925da6d455a: mdadm: update criteria to build with corosync (2017-03-26 13:17:04 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/rpm

[OE-core] [PATCH 1/1] rpm: change PROVIDES rpm-build to RPROVIDES

The rpm 5 has a rpm-build package, so here should use RPROVIDES rather than PROVIDES to keep compatibility. Signed-off-by: Robert Yang --- meta/recipes-devtools/rpm/rpm_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH] ifupdown: Fix initscript

ifupdown does not provide an initscript so this recipe should not inherit update-rc.d class. Instead, we rely on init-ifupdown recipe to startup networking. Signed-off-by: David Vincent --- meta/recipes-core/ifupdown/ifupdown_0.8.16.bb | 5 + 1 file changed, 1

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

Hi Enrico, Am 24.03.2017 um 15:01 schrieb Enrico Joerns: 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