Re: [OE-core] meta/lib/oe/rootfs.py: dont' remove any packages by default

On 07/31/2015 06:46 PM, Paul Eggleton wrote: Hi Robert, On Friday 31 July 2015 14:56:15 Robert Yang wrote: Currently, the rootfs.py removes base-passwd, shadow, update-rc.d, update-alternatives and run-postinsts when package-management not in IMAGE_FEATURES, this causes two problems: 1) This

Re: [OE-core] OEDEM Oct 9, after ELCE and Yocto Project Developer Day

On 7/31/2015 4:56 PM, Philip Balister wrote: > OpenEmbedded will hold a developer meeting Oct 9 after ELCE and YP dev > day in Dublin. > > This is a chance for developers and users of OpenEmbedded (The Yocto > Project build system) to meet and discuss important project issues. > Everyone is welcom

Re: [OE-core] [oe] OEDEM Oct 9, after ELCE and Yocto Project Developer Day

On Fri, Jul 31, 2015 at 11:56 PM, Philip Balister wrote: > OpenEmbedded will hold a developer meeting Oct 9 after ELCE and YP dev > day in Dublin. > > This is a chance for developers and users of OpenEmbedded (The Yocto > Project build system) to meet and discuss important project issues. > Everyo

[OE-core] OEDEM Oct 9, after ELCE and Yocto Project Developer Day

OpenEmbedded will hold a developer meeting Oct 9 after ELCE and YP dev day in Dublin. This is a chance for developers and users of OpenEmbedded (The Yocto Project build system) to meet and discuss important project issues. Everyone is welcome to attend. We are planning on about 30 people so do not

Re: [OE-core] [PATCH 25/26] distrodata.bbclass: do not use get_recipe_pv_without_srcpv() before comparing versions in checkpkg

>>> re.compile("(?P(v|))(?P((\d+[\.\-_]*)+))(?P(\+|)(git|)(r|)(AUTOINC|)(\+|))(?P.*)") >>> regex = re.compile("(?P(v|r|))(?P((\d+[\.\-_]*)+))") > I made a mistake here the case that i say is when have a prefix like, > > >>> import bb > >>> bb.utils.vercmp_string('r2.7+gitX', '2.9+gitX') But the

[OE-core] [PATCH 1/1] opkg: solve inconsistency of using different lists directories

Default behavior of opkg was to use ${OPKGLIBDIR}/opkg/lists; but in our recipe we modify it to ${OPKGLIBDIR}/opkg/${OPKGLIBDIR}/opkg/, when appending package-management to IMAGE_FEATURES these lists are populated during build time (using the default directory), but since our config was different t

[OE-core] [PATCH] init-install-efi.sh: Check if an installation device is present

From: Leonardo Sandoval In case there is no installation device present, give a better message to the user and abort installation. [YOCTO #7971] Signed-off-by: Leonardo Sandoval --- meta/recipes-core/initrdscripts/files/init-install-efi.sh | 5 + 1 file changed, 5 insertions(+) diff --gi

Re: [OE-core] [PATCH 0/4] Fix builds for MIPS64 N32

2015-07-31 13:59 GMT+03:00 Richard Purdie : > On Wed, 2015-07-29 at 18:00 +0300, Dmitry Eremin-Solenikov wrote: >> > Recent check-ins have changed some things. The compile side was working >> > for a >> > while, but not the compilation side (using it). >> > >> > I've been working with RP on IRC,

[OE-core] [PATCH][master|fido|dizzy] base.bbclass: Note when including pn with INCOMPATIBLE_LICENSES

We need to be able to tell people if we WHITELIST a recipe that contains an incompatible licese. Example: If we set WHITELIST_GPL-3.0 ?= "foo", foo will end up on an image even if GPL-3.0 is incompatible. This is the correct behaviour but there is nothing telling people that it is even happening.

Re: [OE-core] [PATCH 25/26] distrodata.bbclass: do not use get_recipe_pv_without_srcpv() before comparing versions in checkpkg

On 31/07/15 10:31, Aníbal Limón wrote: On 31/07/15 10:09, Alexander Kanavin wrote: On 07/31/2015 05:54 PM, Aníbal Limón wrote: I added get_recipe_pv_without_srcpv for compare git versions because vercmp_string don't take into account git versioning (git, gitAUTOINC) causing wrong comparison

Re: [OE-core] [PATCH 25/26] distrodata.bbclass: do not use get_recipe_pv_without_srcpv() before comparing versions in checkpkg

On 31/07/15 10:09, Alexander Kanavin wrote: On 07/31/2015 05:54 PM, Aníbal Limón wrote: I added get_recipe_pv_without_srcpv for compare git versions because vercmp_string don't take into account git versioning (git, gitAUTOINC) causing wrong comparisons. We need to review if removal don't aff

[OE-core] [PATCHv2 2/3] devtool: add --bbpath argument

From: Christopher Larson Signed-off-by: Christopher Larson --- scripts/devtool | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/scripts/devtool b/scripts/devtool index 5d37d3b..1c22438 100755 --- a/scripts/devtool +++ b/scripts/devtool @@ -189,6 +189,7 @@ def

[OE-core] [PATCHv2 3/3] populate_sdk_ext: pass BBPATH to devtool --bbpath

From: Christopher Larson Signed-off-by: Christopher Larson --- meta/classes/populate_sdk_ext.bbclass | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass index 0151468..a36bf16 100644 --- a/meta/clas

[OE-core] [PATCHv2 1/3] populate_sdk_ext: use lnr, not ln -sr, for portability

From: Christopher Larson Not all hosts are running sufficiently new coreutils. Signed-off-by: Christopher Larson --- meta/classes/populate_sdk_ext.bbclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_

[OE-core] [PATCHv2 0/3] Fix a couple populate_sdk_ext issues

From: Christopher Larson - Explicitly pass BBPATH to devtool as Paul Eggleton suggests, to avoid needing to acquire the bitbake lock, to resolve the issue in populate_sdk_ext. - Use the oe-core lnr script rather than ln -sr to improve host portability (not all hosts have recent coreutils).

[OE-core] Yocto Project Status WW31

Current Dev Position: 1.9 Milestone 2 (M2) Next Deadline: M2 cut off of July 27th at noon GMT (on hold, see status) SWAT team rotation: Benjamin -> Juro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * YP 1.9 M2 has been delayed whilst we investigated au

Re: [OE-core] [PATCH 25/26] distrodata.bbclass: do not use get_recipe_pv_without_srcpv() before comparing versions in checkpkg

On 07/31/2015 05:54 PM, Aníbal Limón wrote: I added get_recipe_pv_without_srcpv for compare git versions because vercmp_string don't take into account git versioning (git, gitAUTOINC) causing wrong comparisons. We need to review if removal don't affect the current upstream detection. These are

Re: [OE-core] [PATCH 25/26] distrodata.bbclass: do not use get_recipe_pv_without_srcpv() before comparing versions in checkpkg

Hi Alexander, I added get_recipe_pv_without_srcpv for compare git versions because vercmp_string don't take into account git versioning (git, gitAUTOINC) causing wrong comparisons. We need to review if removal don't affect the current upstream detection. Regards, alimon On 30/07/15 08:3

Re: [OE-core] [PATCH v2 1/2] kernel: Define KERNEL_IMAGETYPE as a list

On Fri, 2015-07-31 at 19:45 +0800, He Zhe wrote: > On 07/31/2015 07:24 PM, Richard Purdie wrote: > > On Wed, 2015-07-22 at 10:29 +0800, He Zhe wrote: > >> On 07/21/2015 10:53 PM, Christopher Larson wrote: > >>> On Tue, Jul 21, 2015 at 12:23 AM, >>> >wrote: > >>> > >>>

Re: [OE-core] [PATCH 0/2] bitbake.conf: add GITHUB_GIT

On Thu, 2015-07-30 at 08:34 -0300, Otavio Salvador wrote: > On Thu, Jul 30, 2015 at 5:32 AM, Olof Johansson > wrote: > > Excerpts from Robert Yang's message of 2015-07-30 09:09:07 +0200: > >> PREMIRRORS is for all the recipes/protocols ? > > > > No, PREMIRRORS is quite expressive, for instance: >

Re: [OE-core] [PATCH 21/26] systemd: remove PV from the recipe

> The idea behind systemd-stable repository is described here: > http://www.freedesktop.org/wiki/Software/systemd/Backports/ > Thanks I didn't know that. > However, it hasn't received any new commits since early May, and still stuck > at v219, so should we update to a new version from the main r

Re: [OE-core] [PATCH 21/26] systemd: remove PV from the recipe

On 07/31/2015 03:53 PM, Alexander Kanavin wrote: The idea behind systemd-stable repository is described here: http://www.freedesktop.org/wiki/Software/systemd/Backports/ However, it hasn't received any new commits since early May, and still stuck at v219, so should we update to a new version fr

Re: [OE-core] [PATCH 21/26] systemd: remove PV from the recipe

On 07/31/2015 03:40 PM, Pascal Bach wrote: I just noticed that specifically systemd-stable repository does not have release tags for new versions at all, and just adds branches for newer versions: http://cgit.freedesktop.org/systemd/systemd-stable/ New tags for systemd are created but not on

Re: [OE-core] [PATCH 21/26] systemd: remove PV from the recipe

Hi Am 30.07.2015 um 18:35 schrieb Alexander Kanavin: > On 07/30/2015 07:25 PM, Burton, Ross wrote: > >> For the release tag I'd agree with you, but as 219 < 219-stable we can't >> just change this now (without adding an epoch, and adding epochs are evil). >> >> Does the RRS have a way of mapping a

Re: [OE-core] [PATCH 21/26] systemd: remove PV from the recipe

On 07/30/2015 07:25 PM, Burton, Ross wrote: For the release tag I'd agree with you, but as 219 < 219-stable we can't just change this now (without adding an epoch, and adding epochs are evil). Does the RRS have a way of mapping a PV to something that can be used in the upstream comparison? I

Re: [OE-core] [PATCH 20/26] stress: use developer's website for SRC_URI

On 07/30/2015 08:45 PM, Max Krummenacher wrote: Please note that the package has now a changed file COPYING for GPLv3 (but the sources still reference GPLv2) So unless you still have stress-1.0.4.tar.gz in your download folder the package checksums and LIC_FILES_CHKSUM will throw an error/warnin

Re: [OE-core] meta/lib/oe/rootfs.py: dont' remove any packages by default

On Fri, Jul 31, 2015 at 1:12 PM, Paul Eggleton wrote: >> I am not sure to understand the relationship between runtime package >> management, and adding/removing users? Why would no runtime package >> management, imply no need to add/remove users? > > I guess the underlying assumption is that if yo

Re: [OE-core] [PATCH v2 1/2] kernel: Define KERNEL_IMAGETYPE as a list

On 07/31/2015 07:24 PM, Richard Purdie wrote: > On Wed, 2015-07-22 at 10:29 +0800, He Zhe wrote: >> On 07/21/2015 10:53 PM, Christopher Larson wrote: >>> On Tue, Jul 21, 2015 at 12:23 AM, >> >wrote: >>> >>> From: He Zhe mailto:zhe...@windriver.com>> >>> >>> To

Re: [OE-core] meta-gplv2? [Was Re: parted_1.8.6.bb: add parted that not GPLv3]

On 07/31/2015 02:14 AM, Andre McCurdy wrote: The number of high quality recipes which can be maintained in oe-core depends on the number of developers actively using and contributing to oe-core. More active developers means more recipes can be maintained to a high quality. My issue here is qua

Re: [OE-core] [PATCH V3 0/4] Fixes for systemd services in systemd

Hello Chen, We are holding our patch for the warning message sysklogd-1.5.1: sysklogd rdepends on initscripts-functions, but it isn't a build dependency? [build-deps] see attached email. Either we need your fix to be merged or allow us to send the patch again. Thanks. Noor -Original Me

Re: [OE-core] [PATCH v2 1/2] kernel: Define KERNEL_IMAGETYPE as a list

On Wed, 2015-07-22 at 10:29 +0800, He Zhe wrote: > On 07/21/2015 10:53 PM, Christopher Larson wrote: > > > > On Tue, Jul 21, 2015 at 12:23 AM, > >wrote: > > > > From: He Zhe mailto:zhe...@windriver.com>> > > > > To support building packaging and installing mult

Re: [OE-core] meta/lib/oe/rootfs.py: dont' remove any packages by default

Hi Nicolas, On Friday 31 July 2015 13:09:29 Nicolas Dechesne wrote: > On Fri, Jul 31, 2015 at 12:46 PM, Paul Eggleton > > wrote: > >> I think that we should not remove any pkgs by default, we can add some > >> interfaces/ways to let the user decide whether to remove them or any > >> other pkgs,

Re: [OE-core] meta/lib/oe/rootfs.py: dont' remove any packages by default

On Fri, Jul 31, 2015 at 12:46 PM, Paul Eggleton wrote: >> I think that we should not remove any pkgs by default, we can add some >> interfaces/ways to let the user decide whether to remove them or any >> other pkgs, for example, add a REMOVE_PACKAGS variable, leave it as NULL >> or only add run-po

Re: [OE-core] meta/lib/oe/rootfs.py: dont' remove any packages by default

On 31/07/15 11:46, Paul Eggleton wrote: Hi Robert, On Friday 31 July 2015 14:56:15 Robert Yang wrote: Currently, the rootfs.py removes base-passwd, shadow, update-rc.d, update-alternatives and run-postinsts when package-management not in IMAGE_FEATURES, this causes two problems: 1) This makes

Re: [OE-core] [PATCH 0/4] Fix builds for MIPS64 N32

On Wed, 2015-07-29 at 18:00 +0300, Dmitry Eremin-Solenikov wrote: > > Recent check-ins have changed some things. The compile side was working > > for a > > while, but not the compilation side (using it). > > > > I've been working with RP on IRC, and he's come up with some additional > > patches.

Re: [OE-core] meta/lib/oe/rootfs.py: dont' remove any packages by default

Hi Robert, On Friday 31 July 2015 14:56:15 Robert Yang wrote: > Currently, the rootfs.py removes base-passwd, shadow, update-rc.d, > update-alternatives and run-postinsts when package-management not > in IMAGE_FEATURES, this causes two problems: > > 1) This makes we can't install the removed pkgs

Re: [OE-core] [poky][PATCH v5] pulseaudio: Revert "launch: Avoid specifically starting PA and rely on autospawn/socket activation"

On Fri, 2015-07-31 at 09:14 +, Zhu Carol wrote: > Hi Tanu, >We had a try about your suggestion " enable autospawning for root by > adding "allow-autospawn-for-root = yes" to client.conf. >It seems an unknown value. >The log is attached: >W: [pulseaudio] main.c: This program is

[OE-core] [PATCH] cross-canadian/gcc: Various mips64 fixes

"n32" is a mips64 variant we need to consider when processing the TARGET_OS extensions. Also add the multilib extensions for mips64. Signed-off-by: Richard Purdie diff --git a/meta/classes/cross-canadian.bbclass b/meta/classes/cross-canadian.bbclass index 832934b..40eb511 100644 --- a/meta/clas

[OE-core] [PATCH] gcc-cross-canadian: Add symlink to real-ld alongside other symlinks

In some cases such as cross architecture configurations (using mips-X-linux on mips64-X-linux), gcc can get confused about finding a 'real' version of ld. Adding a symlink to 'real-ld' allowed these configurations to work properly. Signed-off-by: Richard Purdie diff --git a/meta/recipes-devtools

[OE-core] [PATCH] multilib_global: Fix PREFERRED_VERSION mapping for gcc-cross-canadian

Our multilib cross toolchains have as a prefix however we only have a single gcc-cross-canadian for each arch and it is not prefixed even in the multilib case. We can have two versions of gcc-cross-canadian, 32 and 64 bit. This fixes the multilib PREFERRED_VERSION mapping code so that no prefix i

[OE-core] [PATCH] cross-canadian: Add symlinks for multilib cases

In the same way we map various TARGET_OS options back to the single cross-canadian compiler, add mappings for the TARGET_VENDOR cases we know about in the multilib case. Signed-off-by: Richard Purdie diff --git a/meta/classes/cross-canadian.bbclass b/meta/classes/cross-canadian.bbclass index 40

[OE-core] [PATCH] libgcc: Fix symlink handling in cross-arch multilib cases

The symlink being generated needs to match both the current arch (e.g. mips or mips64) but also use the underlying TARGET_SYS without multilib extensions to TARGET_VENDOR or extensions to TARGET_OS. The way multilib changes TARGET_VENDOR meant this code did not have a way of removing that change.

[OE-core] [PATCH] gcc-multilib-config: Tweak naming of options to match gcc's expectations

gcc itself does not add the '-' of options to its multilib configuration. We should follow its example. Signed-off-by: Richard Purdie diff --git a/meta/recipes-devtools/gcc/gcc-multilib-config.inc b/meta/recipes-devtools/gcc/gcc-multilib-config.inc index bdf4be7..f7f9f55 100644 --- a/meta/recip

[OE-core] [PATCH] gcc: Add patch to handle on target multilibs better

On target multilibs did not work properly since gcc-cross-canadian was only searching a limited number of sysroot directories to find multilib target binaries. This adds an extra search path to ensure those binaries are found and our gcc-cross-canadian works everywhere we need it to, e.g. with mip

[OE-core] [PATCH] packagegroup-cross-canadian: Make the code more readable

Make the code more readable by using the functions slightly differently. Signed-off-by: Richard Purdie diff --git a/meta/recipes-core/packagegroups/packagegroup-cross-canadian.bb b/meta/recipes-core/packagegroups/packagegroup-cross-canadian.bb index 34e6e2b..180dd96 100644 --- a/meta/recipes-co

[OE-core] [PATCH] utils: Handle MLPREFIX in all_multilib_tune_values()

MLPREFIX wasn't being set by the function correctly since its not an overridden value but directly set. Handle this variable explicitly so the function returns the expected values. Signed-off-by: Richard Purdie diff --git a/meta/classes/utils.bbclass b/meta/classes/utils.bbclass index 80e90e8..8

[OE-core] [PATCH] gcc-multilib-config: Adapt mips for mips64 and different gcc versions

The location of some files for mips varies between gcc 4.9 and 5.2. Ensure that we cover both cases (and allow specified files to be optional). Signed-off-by: Richard Purdie diff --git a/meta/recipes-devtools/gcc/gcc-multilib-config.inc b/meta/recipes-devtools/gcc/gcc-multilib-config.inc inde

[OE-core] [PATCH] testimage: testsdk fixes/improvements

The "bitbake meta-toolchain" comment is dated and incorrect, fix to point at -c populate_sdk. If a toolchain contains multiple environment files, iterate them and run the sdk test suite on each on in turn rather than giving a fatal error and giving up. Also improve the debug output so that rather

Re: [OE-core] [PATCH] oeqa/ptest: Modified regex to find FAILED testcases no just FAIL.

Hi Lucian, On Friday 31 July 2015 11:40:25 Lucian Musat wrote: > Some ptests output failed tests as FAILED instead of FAIL, like glib and > pango. > > Bug #6601 > > Signed-off-by: Lucian Musat > --- > meta/lib/oeqa/runtime/_ptest.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

[OE-core] [PATCH 2/2] oe-selftest: devtool: fix teardown warning in test_devtool_update_recipe_append

We don't need to run bitbake -c cleansstate on this because it's being cleaned out as part of "devtool reset". Addresses [YOCTO #8031]. Signed-off-by: Paul Eggleton --- meta/lib/oeqa/selftest/devtool.py | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/lib/oeqa/selftest/devtool.py b/meta

[OE-core] [PATCH 0/2] A couple of devtool fixes

Fix bitbake.lock handling in devtool (must be applied after the bitbake.lock patch just sent to the bitbake list) as well as a warning fix for the devtool oe-selftest tests. The following changes since commit 27d068d05239c26a3848eb101571acab54635e37: harfbuzz: upgrade to 1.0.1 (2015-07-27 23:2

[OE-core] [PATCH 1/2] devtool: use tinfoil shutdown method

Tinfoil now has its own shutdown method, use it instead of calling into cooker - not only is it the right thing to do from an API perspective, it also ensures proper lock handling. Signed-off-by: Paul Eggleton --- scripts/devtool | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --gi

[OE-core] [PATCH] sanity.bbclass: check SSTATE_DIR, DL_DIR and *MIRROR for broken symlinks

This change makes broken symlinks stand out clearly instead of bitbake failing with odd error messages. Tested locally with broken symlink as SSTATE_DIR, DL_DIR and SSTATE_MIRROR. Change-Id: I2e92702237ab3bdb897d0bdefcf33480aabbc288 Signed-off-by: Mikko Rapeli --- meta/classes/sanity.bbclass | 2

Re: [OE-core] [poky][PATCH v5] pulseaudio: Revert "launch: Avoid specifically starting PA and rely on autospawn/socket activation"

Hi Tanu, We had a try about your suggestion " enable autospawning for root by adding "allow-autospawn-for-root = yes" to client.conf. It seems an unknown value. The log is attached: W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).

[OE-core] outdated compat-wireless

meta-openembedded contains a recipe for compat-wireless. According to [1] this is really outdated and replaced by a renamed project called backports[2]. Has anyone tried or plans to replace compat-wireless with this? [1] [2]

Re: [OE-core] [PATCH v2 0/2] Yocto Bug #6945

Ping. On 07/29/2015 09:23 PM, Bruce Ashfield wrote: > On 15-07-29 03:32 AM, He Zhe wrote: >> Ping. >> >> Is there any comments on this? > > I'm obviously ok with the patch in its current RFC status. It works > and I've tested it in my tree (hence why I've been quiet on this > one). > > If it meets

[OE-core] [PATCH] oeqa/ptest: Modified regex to find FAILED testcases no just FAIL.

Some ptests output failed tests as FAILED instead of FAIL, like glib and pango. Bug #6601 Signed-off-by: Lucian Musat --- meta/lib/oeqa/runtime/_ptest.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/runtime/_ptest.py b/meta/lib/oeqa/runtime/_ptest.py index 8

Re: [OE-core] [PATCH v3] mdadm: 3.3.2 -> 3.3.3

Hi, Ross, The mdadm upstream doesn’t provide mdadm.service. So we installed mdmonitor.service just like what Fedora does. And mdmonitor.service is "Software RAID monitoring and management". Cheers, Li From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, July 30, 2015 9:09 PM To: Li,

[OE-core] [PATCH] mesa: upgrade 10.5.8 -> 10.6.3

Tested with X11 : * xf86-video-freedreno (and w/ XA) on IFC6410 and DragonBoard 410c * softpipe on DragonBoard 410c * using meta-qualcomm BSP Signed-off-by: Nicolas Dechesne --- meta/recipes-graphics/mesa/{mesa-gl_10.5.8.bb => mesa-gl_10.6.3.bb} | 0 meta/recipes-graphics/mesa/{mesa_10.5.8.bb =