This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in

This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can

Now after study share state cache in yocto document, I know it can be used by multi build dir to share IPK files. But if all the build dir share the same sstate_cache, why don't they just use the same

Thanks, PACKAGE_INSTALL works great :-) I've gone with the following in my local.conf: PACKAGE_INSTALL_append_pn-core-image-minimal-initramfs = " linux-firmware" -- Chris

To be honest, this package should be in one in core or meta-openembedded. - Armin

Hi, I build a core-image-x11 with beaglebone as machine. I added gstreamer 0.10 support which I will need in Qt. However, I am not able to play a video using xvimagesink like this: gst-launch filesrc

[Re: [yocto] [meta-security][PATCH] libcap-ng: port CVE-2014-3215 patch] On 14.11.29 (Sat 20:51) akuster808 wrote: Yeah, that's on my to-do list for meta-selinux, too. That's the right course of

If using yocto 1.6.1 plugin for Eclipse then selecting help->install new software->add then using http://downloads.yoctoproject.org/releases/eclipse-plugin/1.6.1/kepler works fine. For V1.7 I have

Why share the sstate? Does it contain previously build ipk packages in other build directories for reuse? Regards, Qiang

I solved this problem my own: The package qtbase-plugins has to be added to the image to install the plugins. I also had to add the package qtmultimedia-plugins to install gstreamer plugins and add

Hi everyone, I am trying to build an application using Qt5 Multimedia (playing a video). Yocto is latest 1.6. Qt and my application compile just fine but when I run the application I get this

I am using poky 1.6.1. I have built the follwing images successfully : core-image-sato-sdk & atmel-qt5-demo-image. I am tying to build the following image without success: atmel-qt5-demo-image -c

Create a bbappend file for core-image-minimal-initramfs, and add the following line to the bbappend file. PACKAGE_INSTALL += "linux-firmware" Best Regards, Chen Qi

I would suggest to use separate build directories but let these builds to share downloads and sstate. Regards, Chen Qi On 11/30/2014 12:49 PM, Qiang Yu wrote:

Joe, I went a head and updated to 7.4 which included the security fix. Thanks for the reminder. - Armin

for list of changes see: http://seclists.org/nmap-dev/2014/q3/335 use nmap.inc to house most code. Signed-off-by: Armin Kuster <akuster808@...> --- recipes-security/nmap/{nmap_6.46.bb =>

Hi all, I'm maintaining a Yocto build system to produce these outputs: 1. ARM SOC 1 1). board 1 image 2). board 2 image 3). SDK for i686 4). SDK for x86_64 2. ARM SOC 2 1). board 3 image

0.7.4 - In pscap, remove unused code - Add CAPNG_INIT_SUPP_GRP to capng_change_id - Drop CAP_COMPROMISE_KERNEL - Update the autotools components - Dynamically detect last capability (#895105) - Add

Hello, In a custom recipe I wrote, I want to replace a file that is already added by another package/recipe. I know that normally the proper way to do that would be to use a .bbappend recipe for

Am 28.11.2014 um 14:51 schrieb Anders Darander <anders@...>: In our project we mix the usage of volatiles, symblic links and unionfs. You can take a look into