On Mon, Jul 18, 2016 at 9:45 PM, Max Krummenacher <max.oss...@gmail.com> wrote: > FILESYSTEM_PERMS_TABLES must be set with the relative path from one of the > BBPATH paths. > > Without this patch the setting of FILESYSTEM_PERMS_TABLES disables the use > of openembedded-core/meta/files/fs-perms.txt but, as the file in > meta-angstrom/files/fs-perms-angstrom.txt is not found, that file is not > used for the fixup-perms task. > > With fs-perms-angstrom.txt active files deployed from copydebugsources no > longer trigger these warnings: > | WARNING: helloworld-1.0-r0 do_package_qa: QA Issue: helloworld: > .../src/main.c > | is owned by uid 1000, which is the same as the user running bitbake. This > may > | be due to host contamination [host-user-contaminated] > > Signed-off-by: Max Krummenacher <max.krummenac...@toradex.com> > --- > conf/distro/include/angstrom-core-tweaks.inc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/conf/distro/include/angstrom-core-tweaks.inc > b/conf/distro/include/angstrom-core-tweaks.inc > index 33aaaef..1a3af9d 100644 > --- a/conf/distro/include/angstrom-core-tweaks.inc > +++ b/conf/distro/include/angstrom-core-tweaks.inc > @@ -62,7 +62,7 @@ PACKAGE_CLASSES = "package_ipk" > # Image.bbclass stuff: > > # Override default fs-perms.txt that messes with our /var setup: > -FILESYSTEM_PERMS_TABLES = "fs-perms-angstrom.txt" > +FILESYSTEM_PERMS_TABLES = "files/fs-perms-angstrom.txt" > > # > # udev, devfsd, busybox-mdev (from busybox) or none > -- > 2.6.6 > Do we need fs-perms / for special /var setup - see also base-files? Note that /var/lock configuration is broken causing very ugly effects [1].
[1] https://github.com/schnitzeltony/meta-angstrom/commit/937fb6a41f55132982aba1308aed4fe3f9b82be0 Andreas _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
