Re: [Angstrom-devel] [meta-angstrom][PATCH 1/2] angstrom-core-tweaks.inc: actually use fs-perms-angstrom.txt

[Stefan Agner]

On 2016-07-18 12:45, Max Krummenacher 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 
> ---
>  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

What is the state of this patch? It seems to me that the missing files/
sub directory is really a bug which should be fixed.

--
Stefan

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [meta-angstrom][PATCH 1/2] angstrom-core-tweaks.inc: actually use fs-perms-angstrom.txt

[Max Krummenacher]

Ping.

Max

2016-07-29 15:47 GMT+02:00 Max Krummenacher :
> Hi Andreas
>
> Am Freitag, den 29.07.2016, 13:09 +0200 schrieb Andreas Müller:
>> 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 
>> > ---
>> >  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/937fb6a41f5
>> 5132982aba1308aed4fe3f9b82be0
>>
>> Andreas
>
> My goal is to have the host-user-contaminated warnings go away. They
> occur because the source files are hard linked in do_package and pseudo
> then set them to root:root.
>
> In poky this is fixed with the fs-perms mechanism and the configuration
> file from meta/files/fs-perms.txt.
>
> I then found that Koen's original patch to provide an angstrom fs-perms
> configuration file did in fact disable the use of meta/files/fs
> -perms.txt but did not make available what is in meta-angstrom/files/fs
> -perms-angstrom.txt.
>
> And as there has been some fixes in oe-core since splitting of the fs
> -perms.txt file I tried to backport those which looked not to interfere
> with Koen's intentions with the commit
> 6d518574c11bca1a56ec9b83afd18196a82fbfb0 'angstrom: use custom fs
> -perms.txt that doesn't destroy our /var setup'.
>
> The only symlink created with meta-angstrom/files/fs-perms-angstrom.txt
> is the one Khem added '/var/run -> /run'.
> But that one somehow magically appears also without my patch. Seems
> like base_files does create it already in do_install.
>
> So would you like me to send a v2 of the patch which removes the
> '/var/run -> /run' symlink creation?
>
> Max
>

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [meta-angstrom][PATCH 1/2] angstrom-core-tweaks.inc: actually use fs-perms-angstrom.txt

[Andreas Müller]

On Mon, Jul 18, 2016 at 9:45 PM, Max Krummenacher  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 
> ---
>  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