[OE-core] [RFC] Hybrid live image?

Hi, Attached patch makes the init script attempt to find an writable image to use with Overlay/AUFS, and probably does so poorly. The idea is to eventually allow users to do a "RESET" option in case they mess up the system. The underlying image can be something read-only like cramfs or squashfs.

[OE-core] [PATCH] cmake.bbclass: use weakest ??= assignment for default OECMAKE_SOURCEPATH

Make it slightly easier to support situations where the default path needs to be over-ridden more than once. Signed-off-by: Andre McCurdy --- meta/classes/cmake.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/cmake.bbclass

[OE-core] ✗ patchtest: failure for v86d, qemuboot-x86.inc: use KERNEL_MODULE_AUTOLOAD+KERNEL_MODULE_PROBECONF for uvesafb instead of fbsetup init script

== Series Details == Series: v86d, qemuboot-x86.inc: use KERNEL_MODULE_AUTOLOAD+KERNEL_MODULE_PROBECONF for uvesafb instead of fbsetup init script Revision: 1 URL : https://patchwork.openembedded.org/series/6549/ State : failure == Summary == Thank you for submitting this patch series to

[OE-core] [PATCH] v86d, qemuboot-x86.inc: use KERNEL_MODULE_AUTOLOAD+KERNEL_MODULE_PROBECONF for uvesafb instead of fbsetup init script

* also add UVESA_MODE variable for easier change of resolution and respect it in QB_KERNEL_CMDLINE_APPEND as well * don't use init script just to call modprobe * I wasn't able to test this all the way with runqemu, because runqemu doesn't work on my system, but I've verified that the right

[OE-core] ✗ patchtest: failure for "cdrtools-native: Fix when cc i..." and 2 more (rev2)

== Series Details == Series: "cdrtools-native: Fix when cc i..." and 2 more (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/5743/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests

[OE-core] [PATCH] runqemu-gen-tapdevs: fix runqemu-ifup script call

The tunctl binary is here: OE @ /OE/openembedded-core # find /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/qemu-helper-native/ /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/qemu-helper-native/

Re: [OE-core] [PATCH 3/3] runqemu-gen-tapdevs: Improve help text with an example

FWIW: I've tried to use runqemu for first time (using my own scripts until now). And this example doesn't work for me, the tunctl binary is here: OE @ /OE/openembedded-core # find /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/qemu-helper-native/

[OE-core] [PATCH] selftest/runtime-test: Split the config values

From: Leonardo Sandoval Split the configuration values (common and specific) so it is easier to read what goes into the config file. Also the specific configurations are set in every loop so these do not append on each iteration. Signed-off-by:

[OE-core] [master & pyro][PATCH] useradd-statids.bbclass: Add support for -P / --clear-password option

The commit 31dee7946340bf0f1e94e4e714191d3d6ca3bf6a added a new useradd and groupadd option to specify a clear text password. The parsing logic in the useradd-staticid class did not understand this new option. If the meta-skeleton examples were run with the class enabled an error would be

Re: [OE-core] [PATCH] Check if /etc/fstab exists

On Thu, Apr 27, 2017 at 9:56 AM, Panagiotis Tamtamis wrote: > Using "read-only-rootfs" feature in minimal or special > purpose images (eg mounted images) makes build to fail > because ${IMAGE_ROOTFS}/etc/fstab file does not exist. > > Signed-off-by: Panagiotis

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

On Thu, Apr 27, 2017 at 12:32 PM, Martin Jansa wrote: > Yesterday I've deleted all workspaces where I was getting this error and > since then I haven't seen one. > > So maybe the key to reproduce this was to run builds without the fix > applied and then apply the fix and

[OE-core] [PATCH v2] rootfs-postcommands.bbclass: Check if "/etc/fstab" exists

Using "read-only-rootfs" feature in minimal or special purpose images (eg mounted images) makes build to fail because ${IMAGE_ROOTFS}/etc/fstab file does not exist. Signed-off-by: Panagiotis Tamtamis --- meta/classes/rootfs-postcommands.bbclass | 3 ++- 1 file

[OE-core] ✗ patchtest: failure for Check if /etc/fstab exists

== Series Details == Series: Check if /etc/fstab exists Revision: 1 URL : https://patchwork.openembedded.org/series/6541/ 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

[OE-core] [PATCH] Check if /etc/fstab exists

Using "read-only-rootfs" feature in minimal or special purpose images (eg mounted images) makes build to fail because ${IMAGE_ROOTFS}/etc/fstab file does not exist. Signed-off-by: Panagiotis Tamtamis --- meta/classes/rootfs-postcommands.bbclass | 3 ++- 1 file

Re: [OE-core] [PATCH 1/1] oe-find-native-sysroot: don't clear OECORE_NATIVE_SYSROOT

This worked for me. Tested on sdk and esdk and bitbake std build. Also added info to bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=11409. -brian an intel employee On Mon, Apr 24, 2017 at 8:35 PM, Robert Yang wrote: > The OECORE_NATIVE_SYSROOT may come from

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

Yesterday I've deleted all workspaces where I was getting this error and since then I haven't seen one. So maybe the key to reproduce this was to run builds without the fix applied and then apply the fix and execute another build without removing the tmp-glibc (so that it tries to do incremental

[OE-core] [PATCH] speex: upgrade 1.2rc2 -> 1.2.0

Upgrade speex to 1.2.0. Very small diff between 1.2rc2 and 1.2.0, mostly compiler warning fixes, tabs vs spaces, trailing whitespaces and one liners. Signed-off-by: Marc Ferland --- meta/recipes-multimedia/speex/speex_1.2.0.bb | 19 +++

Re: [OE-core] [PATCH 00/13] Reduce (but not completely eliminate yet) Python 2.x dependencies

On 27 April 2017 at 15:27, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > And a couple of packagegroups list python 2 as well: > - packagegroup-self-hosted > - packagegroup-core-lsb > selfhosted will need it as long as we need it, and I can't imagine LSB has dropped py2... Ross

Re: [OE-core] [PATCH 0/4] Reproducible binaries

SOURCE_DATE_EPOCH is not the issue here. There are few other places that require timestamps. SOURCE_DATE_EPOCH is determined as the mktime of the youngest source file or if git repo present as the time of the top commit. (Otherwise it defaults to 0). This needs to be done per package. I'll send

[OE-core] [PATCH 09/13] python: remove unused 2.x versions of several packages

Nothing is using them in oe-core or meta-oe layers (except python-six is used by and provided in meta-oe, so there was recipe duplication). Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/python/python-async_0.6.2.bb | 5

[OE-core] [PATCH 11/13] mc: do not package Python-based extfs helpers

They have not been ported to Python 3, and they are for browsing Amazon s3+ and Commodore 64/128 emulator filesystems - hardly consequential. Signed-off-by: Alexander Kanavin --- meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 1 -

[OE-core] [PATCH 12/13] parted: move test helper scripts to Python 3

Signed-off-by: Alexander Kanavin --- ...-helper-scripts-used-only-in-tests-to-Pyt.patch | 44 ++ meta/recipes-extended/parted/parted_3.2.bb | 3 +- 2 files changed, 46 insertions(+), 1 deletion(-) create mode 100644

[OE-core] [PATCH 10/13] opkg-utils: move to Python 3

The scripts were fixed to be compatible with py3 some time ago, but the shebang continued to refer to python 2.x. Signed-off-by: Alexander Kanavin --- ...0001-Switch-all-scripts-to-use-Python-3.x.patch | 112 +

[OE-core] [PATCH 07/13] packagegroup-self-hosted: remove python-git dependency

Only python3-git is needed anymore. Signed-off-by: Alexander Kanavin --- meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb

[OE-core] [PATCH 13/13] kconfig-frontends: update to 4.10.0.1

Add a couple of patches: - move python script to use Python 3 - fix .pc file installation path Signed-off-by: Alexander Kanavin --- .../files/0001-Fix-installation-of-.pc-files.patch | 29 ++

[OE-core] [PATCH 08/13] python-pycurl: remove the recipe

Nothing is using it in oe-core or meta-oe layers. Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/python/python-pycurl.inc | 31 -- .../python/python-pycurl/no-static-link.patch | 17

[OE-core] [PATCH 05/13] mklibs-native: remove native python dependency

It's not actually required; host python is fine. Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/mklibs/mklibs-native_0.1.43.bb | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[OE-core] [PATCH 04/13] mesa: drop pythonnative inherit

Mesa is perfectly capable of using host python nowadays. Signed-off-by: Alexander Kanavin --- meta/recipes-graphics/mesa/mesa.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/mesa/mesa.inc

[OE-core] [PATCH 06/13] webkitgtk: remove native python dependency

Using host python seems to be fine. Signed-off-by: Alexander Kanavin --- meta/recipes-sato/webkit/webkitgtk_2.14.5.bb | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/meta/recipes-sato/webkit/webkitgtk_2.14.5.bb

[OE-core] [PATCH 01/13] asciidoc: drop distutils inherit, not actually required

Signed-off-by: Alexander Kanavin --- meta/recipes-extended/asciidoc/asciidoc_8.6.9.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/asciidoc/asciidoc_8.6.9.bb b/meta/recipes-extended/asciidoc/asciidoc_8.6.9.bb index

[OE-core] [PATCH 02/13] bmap-tools: switch to taking source from git

This is where new development happens; in particular Python 3.x support will first appear here: https://github.com/01org/bmap-tools/issues/14 Signed-off-by: Alexander Kanavin --- meta/recipes-support/bmap-tools/bmap-tools_3.2.bb | 9 + 1 file changed,

[OE-core] [PATCH 03/13] mesa: remove the git recipe

It hasn't been touched in almost two years; clearly the idea of providing separate _git.bb recipes is not working. Signed-off-by: Alexander Kanavin --- meta/recipes-graphics/mesa/mesa_git.bb | 22 -- 1 file changed, 22 deletions(-) delete

[OE-core] [PATCH 00/13] Reduce (but not completely eliminate yet) Python 2.x dependencies

This patchset reduces the amount of Python 2.x dependencies in oe-core recipes. Several approaches were taken: 1) If a recipe needs Python 2 only during build to run python scripts, host python is used instead of natively build python. 2) If a recipe needs Python 2 at runtime because it packages

[OE-core] [PATCH] bitbake.conf: Add python2 to HOSTTOOLS

Add python2 to HOSTTOOLS as, according to https://www.python.org/dev/peps/pep-0394/, the command "python2" should be the one used in scripts that are not yet ported to Python 3. Signed-off-by: Diego Rondini --- meta/conf/bitbake.conf | 2 +- 1 file changed, 1

Re: [OE-core] State of bitbake world, Failed tasks 2017-04-26

One of the builds was showing tiptop failure: http://errors.yoctoproject.org/Errors/Details/141293/ I wonder if there is still some undeterministic behavior related to flex. It shouldn't be able to use host's flex due to HOSTTOOLS filtering. It doesn't have the dependency on flex-native, but

Re: [OE-core] Broken NPM builds

On 04/26/2017 11:31 PM, Ilkka Myller wrote: This design allows building static, immutable, OE-proper packages for Node.js based applications while still using standard npm installation process on the build host. This is where OE core npm class differs the most by-design. But are they

Re: [OE-core] Broken NPM builds

On 04/26/2017 11:31 PM, Ilkka Myller wrote: This design allows building static, immutable, OE-proper packages for Node.js based applications while still using standard npm installation process on the build host. This is where OE core npm class differs the most by-design. But are they

Re: [OE-core] [PATCH 0/4] Reproducible binaries

On Wed, 2017-04-26 at 19:50 +, Bystricky, Juro wrote: > > I wasnted to say "passing the seed value" through some separate > > variable > > which is easy to override from somewhere else. > > > > e.g. > > export PRELINK_TIMESTAMP=`git log -1 --pretty=%ct ` > > > > in

[OE-core] State of bitbake world, Failed tasks 2017-04-26

== Number of issues - stats == {| class='wikitable' !|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies!!|Signatures !!colspan='14'|QA !!Comment |- || ||qemuarm ||qemux86 ||qemux86_64

[OE-core] [PATCH v2 1/1] oe.lsb: add get_os_release()

Move get_os_release() from oeqa.utils.metadata to oe.lsb, merging the code with release_dict_osr() from oe.lsb. This removes some code duplication and makes get_os_release() more robust. Signed-off-by: Markus Lehtonen --- meta/lib/oe/lsb.py | 33

[OE-core] [PATCH v2 0/1] oeqa.utils.metadata: cope with invalid lines in os-release file

Total rewrite of the patch, as per Joshua's comments. Refactor and move get_os_release() from oeqa.utils.metadata to oe.lsb. Markus Lehtonen (1): oe.lsb: add get_os_release() meta/lib/oe/lsb.py | 33 - meta/lib/oeqa/utils/metadata.py | 16

Re: [OE-core] [PATCH] oeqa.utils.metadata: cope with invalid lines in os-release file

On 26/04/2017, 17.47, "Joshua Lock" wrote: On Wed, 2017-04-26 at 17:39 +0300, Markus Lehtonen wrote: > Don't crash if every line in /etc/os-release does not adhere to the > expected "key=val" format. E.g. CentOS 7 has empty lines in the file. >