[yocto] [auh][PATCH 07/20] buildhistory.py: replace cleanall with cleansstate

From: Alexander Kanavin It should not be really necessary, and wastes time as the upstream source needs to be re-fetched. Signed-off-by: Alexander Kanavin --- modules/buildhistory.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/buildhistory.py b/modules

[yocto] [auh][PATCH 08/20] testimage.py: do not manipulate branches

From: Alexander Kanavin AUH simply creates a series of commits now, so we can create and run testimage directly on the branch we're on. Signed-off-by: Alexander Kanavin --- modules/testimage.py | 32 1 file changed, 32 deletions(-) diff --git a/mo

[yocto] [auh][PATCH 09/20] Replace references to Aníbal Limón as the maintainer.

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- README | 2 +- upgradehelper.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index e6b0dc2..60dbef9 100644 --- a/README +++ b/README @@ -163,7 +163,7 @@ The latest version of the

[yocto] [auh][PATCH 12/20] utils/git.py: print current dir when git fails

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- modules/utils/git.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/utils/git.py b/modules/utils/git.py index d1fe41b..a6f5422 100644 --- a/modules/utils/git.py +++ b/modules/utils/git.py @@ -40,7 +40,7

[yocto] [auh][PATCH 11/20] upgradehelper.py: remove the package ordering code

From: Alexander Kanavin It was broken and commented out, and not really necessary. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 80 1 file changed, 80 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index

[yocto] [auh][PATCH 13/20] testimage.py: do not call into removed code

From: Alexander Kanavin This was using the removed recipe parsing code to determine if a package supports ptest; it should be replaced with using bitbake API but for now we can simply add all update packages to the list. Signed-off-by: Alexander Kanavin --- modules/testimage.py | 12

[yocto] [auh][PATCH 14/20] testimage.py: add extra logging for the testimage logs retrieval

From: Alexander Kanavin This helped with diagnozing issues described in https://bugzilla.yoctoproject.org/show_bug.cgi?id=12396 Signed-off-by: Alexander Kanavin --- modules/testimage.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/testimage.py b/modules/testimage.py index

[yocto] [auh][PATCH 10/20] modules/recipe: remove

From: Alexander Kanavin The hand-crafted recipe updating/rewriting has been replaced by calling devtool. Signed-off-by: Alexander Kanavin --- modules/recipe/__init__.py | 0 modules/recipe/base.py | 724 - modules/recipe/git.py | 98

[yocto] [auh][PATCH 15/20] upgradehelper.py: fixups to the email message template

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 43 +++ 1 file changed, 27 insertions(+), 16 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d62c9b2..d3cc2c4 100755 --- a/upgradehelper.py +++ b

[yocto] [auh][PATCH 16/20] upgradehelper.py: send email even if recipe upgrade failed

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d3cc2c4..043d334 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -380,8 +380,7 @@ class Updater

[yocto] [auh][PATCH 17/20] upgradehelper.py: add all changes before committing them

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- modules/utils/git.py | 3 +++ upgradehelper.py | 1 + 2 files changed, 4 insertions(+) diff --git a/modules/utils/git.py b/modules/utils/git.py index a6f5422..0e812b9 100644 --- a/modules/utils/git.py +++ b/modules/utils/git.py

[yocto] [auh][PATCH 18/20] upgradehelper.py: when attempting to commit changes do not discard previous errors

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d1f441c..3c41012 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -397,7 +397,6

[yocto] [auh][PATCH 19/20] upgradehelper.py: when recovering from upgrade error, do not refer to a dict entry that may not exist

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 3c41012..58fa0a6 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -510,7 +510,7 @@ class Updater

[yocto] [auh][PATCH 20/20] upgradehelper.py: revert commits that failed to build

From: Alexander Kanavin This helps avoid 'cascading build failures' where one failed update holds up everything else. Signed-off-by: Alexander Kanavin --- modules/utils/git.py | 3 +++ upgradehelper.py | 3 +++ 2 files changed, 6 insertions(+) diff --git a/modules/utils/git.py

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/14/2017 04:13 AM, Robert Yang wrote: How about simply issuing 'git revert' after a build has failed? That's easier to implement than rearranging the order of commits, and the commit message can include a link to the build failure logs. Sounds reasonable to me, I will update the patch.

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/14/2017 06:38 PM, Alexander Kanavin wrote: Got it, thanks. I just sent the patches to yocto@ ML and published them on github - please do try them out, and rebase your patchset on top (some of it may no longer be relevant). I did the rebase myself, and pushed the result here - please

[yocto] [auh][PATCH 00/21] Further enhancements to automatic upgrade helper

ommit fbccfa00967305bb3866d0f610cd4b83b8b7a28c: upgradehelper.py: revert commits that failed to build (2017-12-14 18:13:11 +0200) are available in the Git repository at: git://git.yoctoproject.org/auto-upgrade-helper devel http://git.yoctoproject.org/cgit.cgi/auto-upgrade-helper/log/?h=devel Alexander Kanavi

[yocto] [auh][PATCH 01/21] upgradehelper.py: fix checking for do_checkpkg

From: Robert Yang The error message in the log is: Initialising tasks...ERROR: Task do_checkpkg does not exist for target strace [snip] So line.find("ERROR: Task do_checkpkg does not exist") == 0 doesn't work, use != -1 to fix the problem. Signed-off-by: Robert Yang --- upgradehelper.py | 2

[yocto] [auh][PATCH 02/21] upgradehelper.py: support upgrade multiple recipes

From: Robert Yang Now we can use: $ upgradehelper.py recipe1 recipe2 Signed-off-by: Robert Yang --- upgradehelper.py | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 4797fd8..c81e748 100755 --- a/upgradehelper.py +++ b/upgra

[yocto] [auh][PATCH 03/21] upgradehelper.py: use UniverseUpdater for all cases

From: Robert Yang * Use UniverseUpdater() for the following 3 cases: + Upgrade all recipes + Upgrade 1 recipe - '--maintainer' is not a must when any more when use --send-emails, the maintainer be got from distrodata. + Upgrade multiple recipes * Use "args" as the parameter of Un

[yocto] [auh][PATCH 05/21] upgradehelper.py: only check email settings when -e is specified

From: Robert Yang Fixed: $ upgradehelper.py less ERROR: smtp host not set! Sending emails disabled! ERROR: 'From' address not set! Sending emails disabled! Only check email settings when "-e" is specified can fix the problem. Signed-off-by: Robert Yang --- upgradehelper.py | 3 ++- 1 file cha

[yocto] [auh][PATCH 04/21] modules/steps.py: fix warn when skip compilation

From: Robert Yang Signed-off-by: Robert Yang --- modules/steps.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/steps.py b/modules/steps.py index 63f43c8..5bbe38e 100644 --- a/modules/steps.py +++ b/modules/steps.py @@ -113,7 +113,7 @@ def _compile(bb, pkg, machine

[yocto] [auh][PATCH 06/21] upgradehelper.py: always do upgrade when recipes are specified

From: Robert Yang For example, first run: $ upgradehelper.py less -d 5 It did the upgrade Second run: $ upgradehelper.py less -d 5 DEBUG: Skipping upgrade of less: is in history and not 30 days passed Let it always do the upgrade makes it easier to use when do upgrade locally. It will still do

[yocto] [auh][PATCH 07/21] upgradehelper.py: print info when recipe is skipped to upgrade

From: Robert Yang This makes debug easier. Signed-off-by: Robert Yang --- upgradehelper.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 3c40918..80ea4f4 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -691,11 +691,11

[yocto] [auh][PATCH 08/21] upgradehelper.py: don't build gcc-runtime when --skip-compilation

From: Robert Yang It doesn't make any sense to build it when skip compile. Signed-off-by: Robert Yang --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 80ea4f4..711d3b3 100755 --- a/upgradehelper.py +++ b/upgradeh

[yocto] [auh][PATCH 09/21] upgradehelper.py: drop automatic mode

No longer used since migration to devtool: all upgrades are automatic Signed-off-by: Alexander Kanavin --- README | 6 ++ upgradehelper.py | 6 +- 2 files changed, 3 insertions(+), 9 deletions(-) diff --git a/README b/README index 60dbef9..00a390a 100644 --- a/README +++ b

[yocto] [auh][PATCH 10/21] upgradehelper.py: replace the confusing 'maintainer' command line option

It wasn't clear what the option does, and why it need to be on the command line, so the replacement is a 'global_maintainer_override' config file setting which does the same thing, in a cleaner fashion. Signed-off-by: Alexander Kanavin --- README | 7 ++- upgra

[yocto] [auh][PATCH 11/21] weeklyjob.sh: set up a temporary branch and clean up afterwards

Signed-off-by: Alexander Kanavin --- weeklyjob.sh | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/weeklyjob.sh b/weeklyjob.sh index e2c4b1a..8dd0a1c 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -7,11 +7,23 @@ # # 00 8 * * 6 auh /home/auh/bin

[yocto] [auh][PATCH 12/21] Add support for compiling against non-default C libraries

Particularly, musl is a notorious source of failures and so it's very useful to do at least one build against it by default. Signed-off-by: Alexander Kanavin --- README | 4 +++- modules/utils/bitbake.py | 7 ++- upgradehelper.py | 2 +- 3 files change

[yocto] [auh][PATCH 13/21] Add protection measures and information against running with existing build directories.

This should help e.g. with the following issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7174 Signed-off-by: Alexander Kanavin --- README | 12 upgradehelper.py | 14 ++ weeklyjob.sh | 2 +- 3 files changed, 23 insertions(+), 5 deletions(-) diff

[yocto] [auh][PATCH 15/21] Do not require configuration options that aren't necessary for running ptests

Signed-off-by: Alexander Kanavin --- README | 6 ++ upgradehelper.py | 15 --- 2 files changed, 2 insertions(+), 19 deletions(-) diff --git a/README b/README index 27b0977..acb22ac 100644 --- a/README +++ b/README @@ -122,10 +122,8 @@ file: --- snip

[yocto] [auh][PATCH 14/21] upgradehelper.py: do not include absolute paths in the generated tarball

Signed-off-by: Alexander Kanavin --- upgradehelper.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 9110efc..cb48c47 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -555,9 +555,11 @@ class Updater(object

[yocto] [auh][PATCH 16/21] upgradehelper.py: do not include testimage information in maintainer email messages

Signed-off-by: Alexander Kanavin --- upgradehelper.py | 23 --- 1 file changed, 23 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 5659735..1170ca5 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -290,17 +290,6 @@ class Updater(object):

[yocto] [auh][PATCH 17/21] testimage.py: clarify what arguments are passed to class constructor

Signed-off-by: Alexander Kanavin --- modules/testimage.py | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index 6c4ed2b..86e817c 100644 --- a/modules/testimage.py +++ b/modules/testimage.py @@ -1,4 +1,3 @@ -#!/usr/bin/env

[yocto] [auh][PATCH 18/21] testimage.py: run even if no packages were upgraded

Signed-off-by: Alexander Kanavin --- modules/testimage.py | 4 1 file changed, 4 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index 86e817c..1195916 100644 --- a/modules/testimage.py +++ b/modules/testimage.py @@ -256,10 +256,6 @@ class TestImage(): return

[yocto] [auh][PATCH 19/21] testimage.py: remove all iterations (over machines, over failing recipes)

o the standard integration testimage. Signed-off-by: Alexander Kanavin --- README | 9 +++-- modules/testimage.py | 107 ++- 2 files changed, 9 insertions(+), 107 deletions(-) diff --git a/README b/README index acb22ac..84e140f 1

[yocto] [auh][PATCH 20/21] testimage.py: rewrite the logic for building and running testimages

; this is prone to mistmatches and is best left to a human. Signed-off-by: Alexander Kanavin --- modules/testimage.py | 115 +-- 1 file changed, 10 insertions(+), 105 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index

[yocto] [auh][PATCH 21/21] testimage.py: collect and write out logs from bitbake and testimage

Signed-off-by: Alexander Kanavin --- modules/testimage.py | 31 +++ 1 file changed, 27 insertions(+), 4 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index 699d619..35e23c9 100644 --- a/modules/testimage.py +++ b/modules/testimage.py @@ -49,8

Re: [yocto] Smart Project Manager

On 12/28/2017 01:37 PM, Kirill Kondrashov wrote: Is there some existing C/C++ API for smart pm? I have to interface it from Qt software and wonder if there's some other way rather then just intercepting python scripts output. Upgrade to a recent yocto release, which has replaced dnf with smart

Re: [yocto] Smart Project Manager

On 01/05/2018 05:06 PM, Kirill Kondrashov wrote: Thanks for advice, but at the moment it's a bit of a problem, I'm stuck with poky2.0.3 bound to a specific board, so I will keep up with smart. But what's the benefit of dnf? Talk to the provider of the BSP layer, and ask why you need to be stuc

Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image

On 01/05/2018 06:41 PM, Matt Schepers wrote: This does not install "python3-modules" to the image. When this builds, my python program does not work because of missing dependencies on the standard library. To get this to work I have to go in and append "python3-modules" to IMAGE_INSTALL in my

Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image

On 01/06/2018 08:00 PM, Matt Schepers wrote: How do I check what PN is set to? I can see users-dbg.rpm and users-doc.rpm in the rpm folder. The recipe name is users.bb If the recipe is named users, then PN is most likely users as well. -doc and -dbg are supplementary packages. What is the main

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 11:14 AM, Diaz de Grenu, Jose wrote: I am trying to create a recipe with a post installation script. I am using the following fragment of code (as documented in http://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#new-recipe-post-installation-scripts ): pkg_postins

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 01:44 PM, Diaz de Grenu, Jose wrote: Thanks for the information. I guess this fix will be for Yocto 2.5? Maybe; I'm working right now on the patchset, and will post it to oe-core list later today. Last time it was a bit controversial, so I'd appreciate if you a) try and test it;

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 02:31 PM, Martin Hundebøll wrote: On 2018-01-08 13:19, Alexander Kanavin wrote: The problem is that in Yocto 2.4 then any build which requires on-target postinstallation script is going to trigger warning, even if it is completely correct. Is there no way around this? Is there a

Re: [yocto] Upgrading Yocto Project Version - To Rocko

On 01/09/2018 01:55 PM, Kok, Vincent Chin Keong wrote: I was wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just remove the previous poky folder I downloaded and re-download a newer version of poky and checkout the branch and tags? The easiest is to perform a clean clone of t

Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image

On 01/09/2018 08:45 PM, Matt Schepers wrote: For this recipe the base package is called users.rpm and I can see it in the RPM. Using 'bitbake users -e | grep PN' I was able to find that PN is also set to users, which seems correct. However the recipe does not install python3-modules even thoug

Re: [yocto] [OE-core] liblzma: Memory allocation failed on do_package_rpm

On 01/15/2018 08:20 AM, Manjukumar Harthikote Matha wrote: All, Has anybody seen this error? Finished binary package job, result 0, filename (null) error: create archive failed: cpio: write failed - Cannot allocate memory error: liblzma: Memory allocation failederror: liblzma: Memory allocation

Re: [yocto] Backport of oe-core patch 147074 to rocko

On 01/16/2018 04:32 PM, Jan Siegmund wrote: could commit 953f6d9a717945cc20228e7f75371adc27f4ffbe be added to branch rocko? It fixes breaking packaging when using lz4. Certainly; prepare a patch, and send it to oe-core list with [rocko] prefix. Alex -- _

Re: [yocto] [Pyro] Multiple toolchains

On 01/17/2018 05:59 PM, philippe gislard wrote: We are updating our BSP from Krogoth to Pyro. We are using a kernel designed and patched specifically for our hardware (3.10.40) that does not compile with GCC 5.x or GCC6.x. AFAIK, Pyro is qualified with GCC 5.x and GCC6.x (not with earlier version

[yocto] [auh 2/2] upgradehelper.py: add a reference to License-Update: tag.

Signed-off-by: Alexander Kanavin --- upgradehelper.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 1170ca5..b22b915 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -276,7 +276,9 @@ class Updater(object

[yocto] [auh 1/2] weeklyjob.sh: use -e with auh to actually send the emails

Signed-off-by: Alexander Kanavin --- weeklyjob.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/weeklyjob.sh b/weeklyjob.sh index ac50461..2e8c434 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -20,7 +20,7 @@ git fetch origin git checkout -B tmp-auh-upgrades origin/master

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/17/2018 07:10 PM, Diaz de Grenu, Jose wrote: The patches work, but I was wondering if we really need to mark this behavior as a WARNING. From my point of view, this may be confusing for a user, as it could lead to think that something is wrong. But I think that, even if image post proce

Re: [yocto] Error do_compile libepoxy

On 01/18/2018 10:58 AM, Andrea Galbusera wrote: Looks like my first guess was not that bad. Reverting below commit, which switched to meson build system brought my build back to green. Also CC-ing the patch author who might suggest further investigations. libepoxy: convert to meson build

Re: [yocto] Error do_compile libepoxy

On 01/18/2018 12:00 PM, Martin Jansa wrote: FWIW: here nativesdk-libepoxy fails in do_configure already since meson conversion FileNotFoundError: [Errno 2] No such file or directory: 'TOPDIR/tmp-glibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-libepoxy/1.4.3-r0/build/meson-private/sanitycheck

Re: [yocto] Error do_compile libepoxy

On 01/18/2018 03:41 PM, Andrea Galbusera wrote: Yes, this is coherent with what Alexander's commit message says. We started building stuff in test/ while switching to meson... If we can't easily fix the upstream ourself and/or reproduce outside of OE to ask for help from upstream devels, IMO we s

Re: [yocto] Error do_compile libepoxy

On 01/19/2018 05:29 AM, Andre McCurdy wrote: Note that this same test does build fine in poky, so disabling the tests is not a good fix. You should figure out what is about the non-poky EGL headers that is causing the failure, and whether you need to configure the provider of those headers differ

Re: [yocto] Automated license incompatibility checks

On 01/19/2018 07:21 AM, Boto, Erik (Pelagicore) wrote: I was looking for a way to analyze in more detail how packages of different licenses was used in an image, and stumbled upon this old mail-thread: https://lists.yoctoproject.org/pipermail/yocto/2015-January/023307.html My end goal is prett

Re: [yocto] Error do_compile libepoxy

I'll try to recap a little bit but, please, forgive my ignorance in graphics stacks and libraries. Disclaimer: mostly working on headless systems... my bad! This is what I think I understand here (remember I test building poky + meta-raspberrypi): * libepoxy recipe in poky uses PACKAGECONFIG to

Re: [yocto] Error do_compile libepoxy

On 01/19/2018 06:36 PM, Andrea Galbusera wrote: This is where I think the configuration is not quite right. Instead of virtual/libx11, it should say virtual/libgl. And if that dependency cannot be satisfied, then the x11 option should be altogether disabled in the distro/local config (in poky me

Re: [yocto] Error running testimage under the autobuilder with pyro branch

On 01/28/2018 04:57 PM, Alex Lennon wrote: Hi all, I've got some simple automated testing going to test meta-mono core-image-mono builds. It just bitbakes the image then runs the testimage command This works fine for master and rocko branches, but I get a failure for pyro     Exception: Ty

Re: [yocto] Remove nfs packages from image

On 02/02/2018 12:24 PM, Alexander Kanavin wrote: I think it gets included by default using DISTRO_FEATURES_DEFAULT. So using DISTRO_FEATURES_remove = " nfs" should work. However, you may also want to define your own set of values for your distro for DISTRO_FEATURE

Re: [yocto] Remove nfs packages from image

On 02/02/2018 10:06 AM, Marek Słomiany wrote: I am using yocto rocko, with custom distro (based on poky), and custom image inheriting core-image bbclass. I was asked to get rid of nfs-client and nfs-server (and generaly nfs-anything) from our image. If I'm right it comes with core-image.bbclass.

Re: [yocto] Remove nfs packages from image

On 02/02/2018 12:22 PM, Anuj Mittal wrote: I think it gets included by default using DISTRO_FEATURES_DEFAULT. So using DISTRO_FEATURES_remove = " nfs" should work. However, you may also want to define your own set of values for your distro for DISTRO_FEATURES. https://www.yoctoproject.org/docs/l

Re: [yocto] Getting a recipe's files from within an image recipe

On 02/02/2018 02:16 PM, colin.helliw...@ln-systems.com wrote: I have an app which has a config file, and I'd like my two images (production and dev) to have different configs. Obviously it'd be neater to keep the two config files within the recipe's directory structure. I guess I can't do this in

Re: [yocto] Getting a recipe's files from within an image recipe

On 02/02/2018 02:30 PM, Colin Helliwell wrote: Thanks Alex. I half-had that thought too, but was hoping to do it with the one 'src checkout' of the whole app rather than extra two. Not that that really matters, and it seems it may be the neatest and most robust solution. I believe source che

Re: [yocto] Remove nfs packages from image

On 02/02/2018 03:23 PM, Marek Słomiany wrote: It's still on target: root@target# opkg list |grep nfs libnfsidmap0 - 0.25-r0 nfs-utils - 2.1.1-r0 nfs-utils-client - 2.1.1-r0 nfs-utils-mount - 2.1.1-r0 While checking for any nfs-things using "bitbake -e |grep -v ^# |grep -i nfs" the only intere

Re: [yocto] Creating a python recipe with devtool

On 02/07/2018 02:17 PM, Alan Martinovic wrote: devtool add https://pypi.python.org/packages/65/eb/1c3db9596eddb2bd1d1f8153dcaf2d9f2c7e144f4832d1b1449f681a0a7a/multiprocessing_logging-0.2.6-py2.py3-none-any.whl#md5=b7783a8c449135e5bb344b3f0caa3522 I don't think we support .whl format at the

Re: [yocto] Changing gcc version and arch for single yocto recipe

On 02/07/2018 08:48 PM, Janez Svetokravsky wrote: I have just stumbled upon interesting problem, which i do not know how to solve. I am using yocto to build image for ARM cortex-A9 CPU. default gcc used is version 5.2 Beside ARM cortex-A9 there is cortex-m0plus chip, which is located on the s

Re: [yocto] dnf error

On 02/08/2018 03:17 AM, Russell Peterson wrote: core-image-initramfs-1.0-r0 do_rootfs: Could not invoke dnf Last metadata expiration check: 0:00:00 ago on Thu 08 Feb 2018 12:07:06 AM UTC. Error:  Problem: conflicting requests   - nothing provides /hosttools/python needed by ofa-kernel-4.2-r0

Re: [yocto] [auh] [PATCH] RADME: fix typo on one of the settings

On 02/09/2018 07:26 AM, Chang Rebecca Swee Fun wrote: README | 2 +- There is a typo in the commit message however :) Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dnf error

On 02/09/2018 02:25 AM, Russell Peterson wrote: The package I was adding had python scripts in it. The make process for the package used the python distutils.core setup function. I didn’t write the code… I’m just creating a recipe for it. This in turn copies the scripts to various locations bu

Re: [yocto] [RFC] [auh] [PATCH] upgrade-helper.conf: add a template for easy deployment

On 02/09/2018 07:43 AM, Chang Rebecca Swee Fun wrote: Settings mentioned in the README have been ported over and now users are able to copy and start modifying for personal use cases. This file will served as a reference to minimize errors when users trying to create a new conf file by following

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 02/12/2018 01:40 PM, Diaz de Grenu, Jose wrote: Can you detail how this would be done? Is it possible to append to 'log_check_expected_regex' from the .bb recipe that generates the warning? Or the only option is to patch the poky layer? Is there any way to remove these warnings in rocko wit

[yocto] [PATCH][auh 1/2] upgrade-helper.conf: add a template for easy deployment

From: Chang Rebecca Swee Fun Settings mentioned in the README have been ported over and now users are able to copy and start modifying for personal use cases. This file will served as a reference to minimize errors when users trying to create a new conf file by following the README. Signed-off-b

[yocto] [PATCH][auh 2/2] Improve README and sample config file.

those in a hurry can take it into use immediately. Most settings are specific to a maintainer, and so can't be provided in a 'generic' way. Signed-off-by: Alexander Kanavin --- README | 83 +-- upgr

Re: [yocto] Howto generate a Yocto image with spanish full-support by default

On 02/16/2018 02:17 PM, Iván Castell wrote: After a lot of tests, I have been able to fix this creating these two files:     $ cat /etc/locale.conf     LANG=es_ES.UTF-8     LANGUAGE=es:en     $ cat /etc/profile.d/locale.sh     LC_ALL=es_ES     LANG=es_ES     LANGUAGE=es_ES After rebooti

Re: [yocto] Removing busybox completely from the generated image

On 02/19/2018 10:35 AM, Iván Castell wrote: I have tried breaking apart packagegroup-core-boot, making a copy in my custom layer, removing the line referencing busybox:     ## VIRTUAL-RUNTIME_login_manager ?= "busybox" But now bitbake complains with an error message:     ERROR: Nothing RPRO

[yocto] [auh][PATCH] upgradehelper.py: fix arguments to _pkg_upgradable()

Maintainer whitelisting was broken, in particular. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index b22b915..169e9ce 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -718,7

[yocto] [auh][PATCH] weeklyjob.sh: also clean up the workspace source directory

As devtool does not always remove it. Signed-off-by: Alexander Kanavin --- weeklyjob.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/weeklyjob.sh b/weeklyjob.sh index 2e8c434..412685e 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -24,6 +24,7 @@ $auh_dir/upgradehelper.py -e all

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

On 02/26/2018 04:14 PM, Laigui Qin wrote: I would like to think there is a well maintained Yocto/Poky repository somewhere in the world like the debian/Raspbian deb source to leverage (build and maintain my own repo is not my purpose.) Looks like there is not such repo available... Please con

[yocto] [auh][PATCH] Do not hardcode the location of tmp directory

Get it from bitbake instead. [YOCTO #12566] Signed-off-by: Alexander Kanavin --- upgradehelper.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 169e9ce..d868cde 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -602,9

Re: [yocto] Two packages installing same file (with different content) to rootfs

On 03/10/2018 03:49 AM, Vuille, Martin (Martin) wrote: Ran into an issue where we have two packages installing different content for the same file in rootfs. Whichever gets installed last “wins”. I thought there was a check to prevent this. I’m sure I’ve seen a warning/error like that in the p

[yocto] IMPORTANT: do_patch() fuzz warnings and how to deal with them

*Executive summary* do_patch() will shortly start issuing warnings when recipe patches are applied with some of the patch context ignored. This email explains why this is necessary, and how the warnings can be eliminated. *What is patch fuzz?* Patch fuzz is a situation when the patch tool ig

Re: [yocto] Targeting Windows platform

On 03/14/2018 09:56 AM, Isaac Nickaein wrote: Thanks for sharing your experience. It is relieving to see that you have the same perspective. I hope there will be an initiative to target Windows and I will be glad to contribute. I don't think waiting for the initiative to happen will get you an

Re: [yocto] [matchbox-terminal] main.c: Add support to run user command inside the terminal

On 03/14/2018 04:47 PM, Devarsh Thakkar wrote: Add support for commandline options (--command or -e) using which one can provide commands to run inside the terminal as shown in below command : $matchbox-terminal -e $matchbox-terminal --command Ross, who (if anyone) has write access to th

Re: [yocto] clarify instructions for package feed installation

On 03/15/2018 10:10 PM, Peter A. Bigot wrote: Following the instructions in the 2.4.2 mega-manual section 4.21.4 I set in local.conf:     PACKAGE_FEED_URIS = "http://192.168.65.22/oe/rpi3-sumo";     PACKAGE_FEED_BASE_PATHS = "rpm"     PACKAGE_FEED_ARCHS = "noarch cortexa7hf_neon_vfpv4 raspber

Re: [yocto] package manager contamination in state?

On 03/15/2018 10:12 PM, Peter A. Bigot wrote: While attempting to diagnose a package index problem visible on current poky head I changed local.conf from: PACKAGE_CLASSES ?= "package_rpm" to PACKAGE_CLASSES ?= "package_deb" Note that we don't test deb packaging all that well. I'm not even su

[yocto] [PATCH][AUH] Add a commit_revert_policy configuration setting

upgrade commit, so that each upgrade is effectively built against master, which makes it less likely to fail. Signed-off-by: Alexander Kanavin --- upgrade-helper.conf | 13 + upgradehelper.py| 6 +- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/upgrade-helper.conf

Re: [yocto] [OE-core] Yocto Project Status WW12’18

On 03/19/2018 10:07 PM, Burton, Ross wrote: Do we have a place identified for new changes (2.6) while 2.5 stabilizes. A formal place, no.  I tend to queue stuff in a branch if master isn't taking all of my energy, otherwise the patches will sit on the list until 2.5 releases.  Typical

Re: [yocto] [OE-core] Yocto Project Status WW12’18

On 03/20/2018 12:52 PM, Burton, Ross wrote: Which brings me to a question: what is a good schedule and cadence for AUH runs? Currently it's run on the 15th of every odd-numbered month (so January, March, and so on), but I thought of shifting it one month forward, so it doesn't lan

Re: [yocto] [OE-core] Yocto Project Status WW12’18

On 03/20/2018 05:59 PM, Richard Purdie wrote: How long does a single run take, and why not run it every month? Just a bit longer than a day, maybe 30 hours, if it needs to update the typical amount of 100-150 packages. I'll shift it to monthly then. Personally I'm leaning to every couple of we

Re: [yocto] Yocto and NPM issues

On 03/21/2018 03:09 PM, Svein Seldal wrote: Hi I'm attempting to package a npm-based js application into a Rocko image, and I'm having some issues. For testing I use the official poky repo and the meta-openembedded repo (for installing nodejs 8.4.0). I'm building for qemux86-64. I know this

Re: [yocto] Yocto and NPM issues

On 03/21/2018 03:54 PM, Alexander Kanavin wrote: I'm attempting to package a npm-based js application into a Rocko image, and I'm having some issues. For testing I use the official poky repo and the meta-openembedded repo (for installing nodejs 8.4.0). I'm building for qemux

Re: [yocto] [OE-core] Yocto Project Status WW12’18

On 03/21/2018 04:24 PM, Philip Balister wrote:     Which brings me to a question: what is a good schedule and cadence     for AUH runs? Currently it's run on the 15th of every odd-numbered     month (so January, March, and so on), but I thought of shifting it     one month forward, so it does

Re: [yocto] Yocto and NPM issues

On 03/21/2018 04:44 PM, Svein Seldal wrote: > Oh, and you might have more success using meta-nodejs, as it doesn't try > to implement a custom fetcher, and just runs npm directly during the > build. If you don't mind that that makes the build outcome essentially > random from one invocation

Re: [yocto] Building BlueZ from git in Yocto

On 03/21/2018 05:47 PM, Alan Martinovic wrote: When you say "tagged as backports" are you referring to the Upstream-Status? So this is a backport patch: Upstream-Status: Accepted [https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=76255f73 2d68aef2b90d36d9c7be51a9e1739ce7] b

[yocto] [PATCH 2/2] When 'devtool upgrade' fails to rebase patches, stop and report a failure

Previously it would continue, which eventually resulted in an unhelpful, generic error message printed by 'devtool finish'. Signed-off-by: Alexander Kanavin --- modules/steps.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/modules/steps.py b/modules/step

[yocto] [PATCH 1/2] Do not skip packages that were attempted recently.

This was undocumented and made a number of hardcoded assumptions. The options were to make it configurable, or just remove the logic, and I chose the latter. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 40 1 file changed, 40 deletions

Re: [yocto] [PATCH 1/2] Do not skip packages that were attempted recently.

On 03/21/2018 06:19 PM, Alexander Kanavin wrote: This was undocumented and made a number of hardcoded assumptions. The options were to make it configurable, or just remove the logic, and I chose the latter. Uh, forgot to add the [auh] prefix to these two. Alex

<    1   2   3   4   >