Oh and another point I forgot: some files are created at do_rootfs time when packages are installed onto the image, so they won't be caught by this check at all. Better to do it at the last

I think this situation is an image configuration problem, not a package qa problem. If a package wants to install something in a location that is deemed inappropriate by the local config, there's a

Hi, /dev/null in pseudo with -r does not work as expected (see commands below). For example fakechroot behaves as I expected (see below). Can I obtain similar behavior like fakechroot using

You might also consider some form of path normalization if you’re comparing directly like this, otherwise i.e. //foo wouldn’t match /foo, even though it’s the same path.-- Christopher

Unless I’m missing something, you aren’t checking for startswith(p + os.sep), so a file in libexec would match a prohibited path of lib, as it’d still start with that, no?-- Christopher

Chris figured this out and reported back on the IRC channel - turns out that in his configuration, "at" was in PACKAGE_EXCLUDE. Unfortunately dnf is not being very clear about why the package is

Add documentation for the prohibited-path QA test and associated PROHIBITED_PATH variable. Signed-off-by: Martyn Welch <martyn.welch@...> --- Changes since v1: - Correcting author and

Sometimes we wish to ensure that packages don't install files or directories somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed

Add documentation for the prohibited-path QA test and associated PROHIBITED_PATH variable. Signed-off-by: Martyn Welch <martyn@...> --- documentation/ref-manual/ref-classes.xml | 5

From: Fabien Lahoudere <fabien.lahoudere@...> Sometimes we wish to ensure that packages don't install files or directories somewhere that may prove detrimental to the operation of

Hey, I have a weird issue when generating an SDK for the image I'm building. Somehow, I end up with the following errors: $ bitbake -c populate_sdk core-image-pelux-minimal ERROR:

Well at is part of oe-core so that should have been built. "bitbake at" to see why, or if that works then rebuilding your image should work (although it really should have been built already). Ross

> ./poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.4.5.bb As I recall, these versions are very very old... plugins-base_1.4.5 (September 2015, or even older)?! Just kludge! Zoran

Hello Chris, I could not give you some viable advice regarding YOCTO (I see that you are using lot of layers): meta meta-poky meta-yocto-bsp =

Current Dev Position: YP 2.5 Planning and M1 development Next Deadline: YP 2.5 M1 cut off of 12/4/17 SWAT team rotation: Leo -> Juro on Nov. 10, 2017. SWAT team rotation: Juro -> Paul on Nov.17,

Chris Hughes <89dragon@...> wrote: Make sure all layer dependencies are included into the conf/bblayers.conf file. There must be at least one recipe that either implicity (by default, a recipe

Ran Shalit <ranshalit@...> wrote: There is a specific varible which you can use to point to a specific PV,

From previous emails, I can see that your major concern is about SDK and application development. And you want to keep SDK in sync across different hosts. eSDK and devtool in new Yocto

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can

Hi Ulf, coreutils already does override busybox when installed, at least where the alternatives definitions are set up. I'm not sure if the definitions are complete though. Surely the answer to