[yocto] QA cycle report for 2.6 M4 RC1

Hello All, This is the full report for 2.6 M4 RC1: https://wiki.yoctoproject.org/wiki/WW44_-_2018-10-30_-_Full_Test_Cycle_2.6_M4_RC1 Summary All planned tests were executed. Total Test Executed - 3339 Passed Test - 3322 Failed Test - 7 Blocked Test - 4 There were zero high pr

[yocto] [PATCH] update-rc.d: support enable/disable function

From: Changqing Li Add support of enable/disable function, so that user can keep previous config after upgrade package Signed-off-by: Changqing Li --- update-rc.d | 70 + 1 file changed, 70 insertions(+) diff --git a/update-rc.d b/up

[yocto] [PATCH] ref-variables.xml: update manual page for update-rc.d

From: Changqing Li Currently, yocto doc refer link http://www.tin.org/bin/man.cgi? section=8&topic=update-rc.d. as man page of update-rc.d, but lastest debian udpate-rc.d have big difference with ours, they need insserv and all the initscripts support LSB comment header. change to new link which

Re: [yocto] Set linux capabilities on binary on a recipe in meta-oe layer

Thanks Piotr, that worked! How can this be achieved when the rootfs is created and not on first boot? I would like not to ship libcap binaries with the target in production. /Markus On Thu, 8 Nov 2018 at 22:53, Piotr Tworek wrote: > Hi Markus, > > Have you tried doing it in the postinst step e

[yocto] Autoincing version every rebuild

Hi all. I'd like increment version number (PV) o release number (PR) every time I built a recipe. I use this strategy in debug mode to give a reference to every debug session. In production it PV and PR value for the recipe will be fixed. Any idea? I'm working with fsl 4.1.15-2.0.1 Best r

[yocto] [yocto-autobuilder-helper][PATCH] config.json: Disable BUILDINFO for oe-selftest

Currently the containerimage.ContainerImageTests.test_expected_files test doesn't expect a file at /etc/build so BUILDINFO must be false for the test to pass. Signed-off-by: Michael Halstead --- config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/config.json b/config.json index 6288e

[yocto] non-existent task do_package_write_ipk

Hi There, I'm not able to inherit core-image into my recipe, when I do, I get the following error: ERROR: Task do_populate_sdk in .../poky/meta/recipes-core/images/ core-image-base.bb rdepends upon non-existent task do_package_write_ipk in /home/donal/Projects/farkas/source/meta-my-platform/recipes

Re: [yocto] Autoincing version every rebuild

Use the PR service, that's exactly what this is for. Ross On Fri, 9 Nov 2018 at 10:51, Mauro Ziliani wrote: > > Hi all. > > I'd like increment version number (PV) o release number (PR) every time > I built a recipe. > > I use this strategy in debug mode to give a reference to every debug > sessio

Re: [yocto] non-existent task do_package_write_ipk

A recipe that ship files and generates packages can't also inherit core-image because it can't both be a package and an image. If you want this package to run something when it is installed, write a post-install function (pkg_postinst). Ross On Fri, 9 Nov 2018 at 11:35, Donal Morrissey wrote: >

Re: [yocto] [patchtest-oe][PATCH] test_patch_cve.py: fix cve tag checking logic

When updating patchtest-oe to include the CVE fixes I also cleaned up repositories in the share directory removing the patchwork credentials in the process. I've restored the patchwork credentials and posted the test results from local backups. I've opened a bug to collect ideas for testing patcht

[yocto] so how does PACKAGECONFIG_remove really work?

Hi, Can any one please help me to understand PACKAGECONFIG_remove feature Let's take an example of systemd recipe as follows: PACKAGECONFIG ??= "vconsole" PACKAGECONFIG[vconsole] = "-Dvconsole=true,-Dvconsole=false,,${PN}-vconsole-setup" Now how should we disable features set in PACKAGECON

Re: [yocto] Set linux capabilities on binary on a recipe in meta-oe layer

Hi! On Fri, Nov 9, 2018 at 12:16 PM Markus W markus4dev-at-gmail.com wrote: > On Thu, 8 Nov 2018 at 22:53, Piotr Tworek wrote: ... >> pkg_postinst_ontarget_${PN} () { >>setcap cap_net_raw+eip $D${bindir}/node >> } ... > How can this be achieved when the rootfs is created and not on first >

Re: [yocto] so how does PACKAGECONFIG_remove really work?

Hi, Can any one please help me to understand PACKAGECONFIG_remove feature Let's take an example of systemd recipe as follows: PACKAGECONFIG ??= "vconsole" PACKAGECONFIG[vconsole] = "-Dvconsole=true,-Dvconsole=false,,${PN}-vconsole-setup" Now how should we disable features set in PACKAGECON

Re: [yocto] so how does PACKAGECONFIG_remove really work?

On Fri, 9 Nov 2018 at 14:36, Aditya Tayade wrote: > Can any one please help me to understand PACKAGECONFIG_remove feature > > > Let's take an example of systemd recipe as follows: > > PACKAGECONFIG ??= "vconsole" > > PACKAGECONFIG[vconsole] = > "-Dvconsole=true,-Dvconsole=false,,${PN}-vconsole-se

[yocto] core-image-weston w/ initramfs

so core-image-weston works fine with the touch screen, then we added core-image-minimal initramfs so we could boot with encrypted filesystem, however now it seems the touch screen has lost its touch and pointed capabilities, ive determined that much by looking at the logs for when weston fails, sam

Re: [yocto] non-existent task do_package_write_ipk

Hi Ross, Thank you for your help. My build is using a layer which is generating a file in a ROOTFS_POSTPROCESS_COMMAND command. I would like to modify this file as part of the yocto build, but I'd prefer not to modify/fork this layer as it is from a vender. I'm creating my own layer, which will mo

Re: [yocto] non-existent task do_package_write_ipk

On Fri, 9 Nov 2018 at 14:48, Donal Morrissey wrote: > Thank you for your help. My build is using a layer which is generating a file > in a ROOTFS_POSTPROCESS_COMMAND command. I would like to modify this file as > part of the yocto build, but I'd prefer not to modify/fork this layer as it > is f

Re: [yocto] so how does PACKAGECONFIG_remove really work?

On Fri, Nov 9, 2018 at 4:41 PM Burton, Ross ross.burton-at-intel.com wrote: > > On Fri, 9 Nov 2018 at 14:36, Aditya Tayade wrote: > > Can any one please help me to understand PACKAGECONFIG_remove feature > > > > > > Let's take an example of systemd recipe as follows: > > > > PACKAGECONFIG ??= "vc

Re: [yocto] so how does PACKAGECONFIG_remove really work?

Thanks Ross. Regards, Aditya Tayade From: Burton, Ross Sent: Friday, November 9, 2018 8:10:22 PM To: Aditya Tayade Cc: Yocto-mailing-list Subject: Re: [yocto] so how does PACKAGECONFIG_remove really work? On Fri, 9 Nov 2018 at 14:36, Aditya Tayade wrote: > Ca

Re: [yocto] non-existent task do_package_write_ipk

Hi Ross, I had to use IMAGE_PREPROCESS_COMMAND in my own image recipe, the execution order of the ROOTFS_POSTPROCESS_COMMAND commands didn't work for me. Thanks for your help. Donal On Fri, 9 Nov 2018 at 14:53, Burton, Ross wrote: > On Fri, 9 Nov 2018 at 14:48, Donal Morrissey > wrote: > > Than

Re: [yocto] [RFC] Yocto Autobuilder and LAVA Integration

On Thu, 8 Nov 2018 at 20:49, Chan, Aaron Chun Yew < aaron.chun.yew.c...@intel.com> wrote: > Hi Anibal/RP, > > > In order to do a distributed Boards testing the Yocto Autobuilder > > needs to publish in some place accessible the artifacts (image, > > kernel, etc) to flash/boot the board and the tes

[yocto] Issue using UEFI with rootfs(squashfs) generated as a wic

Hello, The platform is running on a i7 CPU and is using UEFI to load the kernel. The image that we are currently building is loading out of a USB stick wish was working until I switched the rootfs type to squashfs. Systemd-boot is as the boot loader. So far what I noticed is the boot.conf

Re: [yocto] QA cycle report for 2.6 M4 RC1

On 11/9/18 1:24 AM, Jain, Sangeeta wrote: > >   > > Hello All, > >   > Thank you to the Intel and Wind QA teams for performing these tasks. Will the Build appliance failure keep it from functioning ? - armin > This is the full report for 2.6 M4 RC1:  > > https://wiki.yoctoproject.org/wiki/WW