Lots of [host-user-contaminated] warning

Lots of [host-user-contaminated] warning

[Andreas Müller]

Hi,

this bugs me for a while and I wonder if I am again the only one
facing this: I get floods of warnings for sourcecode files as

WARNING: QA Issue: qtserialport:
/qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
is owned by uid 1000, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
WARNING: QA Issue: qtx11extras:
/qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
is owned by uid 1000, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
WARNING: QA Issue: qtxmlpatterns:
/qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
is owned by uid 1000, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]

I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.

Help appreciated

Andreas

Re: Lots of [host-user-contaminated] warning

[Max Krummenacher]

Hi Andreas

Am Dienstag, den 17.11.2015, 09:46 +0100 schrieb Andreas Müller:
> Hi,
> 
> this bugs me for a while and I wonder if I am again the only one
> facing this: I get floods of warnings for sourcecode files as
> 
> WARNING: QA Issue: qtserialport:
> /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1
+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: qtx11extras:
> /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1
+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: qtxmlpatterns:
> /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1
+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> 
> I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
> set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
> 
> Help appreciated
> 
> Andreas

I see this also in my builds. The warnings clutter the build output in a
way that makes the warnings mostly useless. Who will spot the one
important new warning in the hundreds of host-user-contaminated ones?
A fresh build of core-image-minimal today gave me 54 of these warnings.
All but one (glibc-locale) complaining on source files.

I checked a few recipes and most of them were not even using a custom
do_install but autotools generated 'make install' with something like
'cp -p src/* dest/' or so.

Even if I know how to do it I think we should not patch upstream sources
to suppress a warning introduced by the downstream build system with
loads of false positives and then have to maintain the patches as
upstream is progressing.

I haven't looked into how one does it but I'm inclined to switch of the
warning globally, e.g. in local.conf.

Max

Re: Lots of [host-user-contaminated] warning

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 3168 bytes --]

On Fri, Nov 20, 2015 at 4:02 AM, Max Krummenacher <max.oss.09@gmail.com>
wrote:

> Am Dienstag, den 17.11.2015, 09:46 +0100 schrieb Andreas Müller:
> > Hi,
> >
> > this bugs me for a while and I wonder if I am again the only one
> > facing this: I get floods of warnings for sourcecode files as
> >
> > WARNING: QA Issue: qtserialport:
> > /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1
> +gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
> > is owned by uid 1000, which is the same as the user running bitbake.
> > This may be due to host contamination [host-user-contaminated]
> > WARNING: QA Issue: qtx11extras:
> > /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1
> +gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
> > is owned by uid 1000, which is the same as the user running bitbake.
> > This may be due to host contamination [host-user-contaminated]
> > WARNING: QA Issue: qtxmlpatterns:
> > /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1
> +gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
> > is owned by uid 1000, which is the same as the user running bitbake.
> > This may be due to host contamination [host-user-contaminated]
> >
> > I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
> > set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
> >
> > Help appreciated
> >
> > Andreas
>
> I see this also in my builds. The warnings clutter the build output in a
> way that makes the warnings mostly useless. Who will spot the one
> important new warning in the hundreds of host-user-contaminated ones?
> A fresh build of core-image-minimal today gave me 54 of these warnings.
> All but one (glibc-locale) complaining on source files.
>
> I checked a few recipes and most of them were not even using a custom
> do_install but autotools generated 'make install' with something like
> 'cp -p src/* dest/' or so.
>

Yes, this is the most common case. Usage of cp -a or cp -p means the build
ownership is retained, and no chown is run to fix it.


> Even if I know how to do it I think we should not patch upstream sources
> to suppress a warning introduced by the downstream build system with
> loads of false positives and then have to maintain the patches as
> upstream is progressing.
>

Either we're calling the upstream buildsystem and not running cp directly,
in which case it's a bug in the upstream buildsystem, since make install
will result in non-deterministic behavior in the ownership of the installed
files, or it's a cp -a case, which doesn't require altering upstream with a
patch at all, only recipe modification.


> I haven't looked into how one does it but I'm inclined to switch of the
> warning globally, e.g. in local.conf.


Blindly disabling them will just result in ignoring a problem. Files in the
target filesystem are owned by your build user, who most likely doesn't
even exist on target.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 4039 bytes --]

Re: Lots of [host-user-contaminated] warning

[Phil Reid]

On 18/01/2016 10:55 AM, Christopher Larson wrote:
>
> On Fri, Nov 20, 2015 at 4:02 AM, Max Krummenacher <max.oss.09@gmail.com <mailto:max.oss.09@gmail.com>> wrote:
>
>     Am Dienstag, den 17.11.2015, 09:46 +0100 schrieb Andreas Müller:
>     > Hi,
>     >
>     > this bugs me for a while and I wonder if I am again the only one
>     > facing this: I get floods of warnings for sourcecode files as
>     >
>     > WARNING: QA Issue: qtserialport:
>     > /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1
>     +gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
>     > is owned by uid 1000, which is the same as the user running bitbake.
>     > This may be due to host contamination [host-user-contaminated]
>     > WARNING: QA Issue: qtx11extras:
>     > /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1
>     +gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
>     > is owned by uid 1000, which is the same as the user running bitbake.
>     > This may be due to host contamination [host-user-contaminated]
>     > WARNING: QA Issue: qtxmlpatterns:
>     > /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1
>     +gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
>     > is owned by uid 1000, which is the same as the user running bitbake.
>     > This may be due to host contamination [host-user-contaminated]
>     >
>     > I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
>     > set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
>     >
>     > Help appreciated
>     >
>     > Andreas
>
>     I see this also in my builds. The warnings clutter the build output in a
>     way that makes the warnings mostly useless. Who will spot the one
>     important new warning in the hundreds of host-user-contaminated ones?
>     A fresh build of core-image-minimal today gave me 54 of these warnings.
>     All but one (glibc-locale) complaining on source files.
>
>     I checked a few recipes and most of them were not even using a custom
>     do_install but autotools generated 'make install' with something like
>     'cp -p src/* dest/' or so.
>
>
> Yes, this is the most common case. Usage of cp -a or cp -p means the build ownership is retained, and no chown is run to fix it.
>
>     Even if I know how to do it I think we should not patch upstream sources
>     to suppress a warning introduced by the downstream build system with
>     loads of false positives and then have to maintain the patches as
>     upstream is progressing.
>
>
> Either we're calling the upstream buildsystem and not running cp directly, in which case it's a bug in the upstream buildsystem, since make install will result
> in non-deterministic behavior in the ownership of the installed files, or it's a cp -a case, which doesn't require altering upstream with a patch at all, only
> recipe modification.
>
>     I haven't looked into how one does it but I'm inclined to switch of the
>     warning globally, e.g. in local.conf.
>
>
> Blindly disabling them will just result in ignoring a problem. Files in the target filesystem are owned by your build user, who most likely doesn't even exist
> on target.

For me the issues are all reported with -dbg packages.
All are source files in /<packagename>-dbg/usr/src/debug/<packagename>/...
Last build had 126 packages with the warning.
Including things like:
gcc-linaro-4.9: gcc: 
/gcc-dbg/usr/src/debug/gcc/linaro-4.9-r2015.06/gcc-linaro-4.9-2015.06/build.arm-angstrom-linux-gnueabi.arm-angstrom-linux-gnueabi/gcc/tm-preds.h is owned by uid 
1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
systemd-226+gitAUTOINC+4211d5bd13: systemd: /systemd-dbg/usr/src/debug/systemd/1_226+gitAUTOINC+4211d5bd13-r0/git/src/udev/scsi_id/scsi_serial.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]
perl-5.22.0: perl: /perl-dbg/usr/src/debug/perl/5.22.0-r0/perl-5.22.0/ext/re/re_exec.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]



-- 
Regards
Phil Reid

Re: Lots of [host-user-contaminated] warning

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 4797 bytes --]

On Sun, Jan 17, 2016 at 8:10 PM, Phil Reid <preid@electromag.com.au> wrote:

> On 18/01/2016 10:55 AM, Christopher Larson wrote:
>
>
>> On Fri, Nov 20, 2015 at 4:02 AM, Max Krummenacher <max.oss.09@gmail.com
>> <mailto:max.oss.09@gmail.com>> wrote:
>>
>>     Am Dienstag, den 17.11.2015, 09:46 +0100 schrieb Andreas Müller:
>>     > Hi,
>>     >
>>     > this bugs me for a while and I wonder if I am again the only one
>>     > facing this: I get floods of warnings for sourcecode files as
>>     >
>>     > WARNING: QA Issue: qtserialport:
>>     > /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1
>>     +gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
>>     > is owned by uid 1000, which is the same as the user running bitbake.
>>     > This may be due to host contamination [host-user-contaminated]
>>     > WARNING: QA Issue: qtx11extras:
>>     > /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1
>>     +gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
>>     > is owned by uid 1000, which is the same as the user running bitbake.
>>     > This may be due to host contamination [host-user-contaminated]
>>     > WARNING: QA Issue: qtxmlpatterns:
>>     > /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1
>>     +gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
>>     > is owned by uid 1000, which is the same as the user running bitbake.
>>     > This may be due to host contamination [host-user-contaminated]
>>     >
>>     > I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few
>> recipes
>>     > set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
>>     >
>>     > Help appreciated
>>     >
>>     > Andreas
>>
>>     I see this also in my builds. The warnings clutter the build output
>> in a
>>     way that makes the warnings mostly useless. Who will spot the one
>>     important new warning in the hundreds of host-user-contaminated ones?
>>     A fresh build of core-image-minimal today gave me 54 of these
>> warnings.
>>     All but one (glibc-locale) complaining on source files.
>>
>>     I checked a few recipes and most of them were not even using a custom
>>     do_install but autotools generated 'make install' with something like
>>     'cp -p src/* dest/' or so.
>>
>>
>> Yes, this is the most common case. Usage of cp -a or cp -p means the
>> build ownership is retained, and no chown is run to fix it.
>>
>>     Even if I know how to do it I think we should not patch upstream
>> sources
>>     to suppress a warning introduced by the downstream build system with
>>     loads of false positives and then have to maintain the patches as
>>     upstream is progressing.
>>
>>
>> Either we're calling the upstream buildsystem and not running cp
>> directly, in which case it's a bug in the upstream buildsystem, since make
>> install will result
>> in non-deterministic behavior in the ownership of the installed files, or
>> it's a cp -a case, which doesn't require altering upstream with a patch at
>> all, only
>> recipe modification.
>>
>>     I haven't looked into how one does it but I'm inclined to switch of
>> the
>>     warning globally, e.g. in local.conf.
>>
>>
>> Blindly disabling them will just result in ignoring a problem. Files in
>> the target filesystem are owned by your build user, who most likely doesn't
>> even exist
>> on target.
>>
>
> For me the issues are all reported with -dbg packages.
> All are source files in /<packagename>-dbg/usr/src/debug/<packagename>/...
> Last build had 126 packages with the warning.
> Including things like:
> gcc-linaro-4.9: gcc:
> /gcc-dbg/usr/src/debug/gcc/linaro-4.9-r2015.06/gcc-linaro-4.9-2015.06/build.arm-angstrom-linux-gnueabi.arm-angstrom-linux-gnueabi/gcc/tm-preds.h
> is owned by uid 1000, which is the same as the user running bitbake. This
> may be due to host contamination [host-user-contaminated]
> systemd-226+gitAUTOINC+4211d5bd13: systemd:
> /systemd-dbg/usr/src/debug/systemd/1_226+gitAUTOINC+4211d5bd13-r0/git/src/udev/scsi_id/scsi_serial.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]
> perl-5.22.0: perl:
> /perl-dbg/usr/src/debug/perl/5.22.0-r0/perl-5.22.0/ext/re/re_exec.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]


Sounds like a bug in the packaging code, likely straightforward to resolve.
Open a bug in the bug tracking system.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 5677 bytes --]

Re: Lots of [host-user-contaminated] warning

[Max Krummenacher]

Am Sonntag, den 17.01.2016, 19:55 -0700 schrieb Christopher Larson:
> On Fri, Nov 20, 2015 at 4:02 AM, Max Krummenacher <
> max.oss.09@gmail.com>
> wrote:
> 
> > Am Dienstag, den 17.11.2015, 09:46 +0100 schrieb Andreas Müller:
> > > Hi,
> > > 
> > > this bugs me for a while and I wonder if I am again the only one
> > > facing this: I get floods of warnings for sourcecode files as
> > > 
> > > WARNING: QA Issue: qtserialport:
> > > /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1
> > +gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
> > > is owned by uid 1000, which is the same as the user running
> > > bitbake.
> > > This may be due to host contamination [host-user-contaminated]
> > > WARNING: QA Issue: qtx11extras:
> > > /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1
> > +gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
> > > is owned by uid 1000, which is the same as the user running
> > > bitbake.
> > > This may be due to host contamination [host-user-contaminated]
> > > WARNING: QA Issue: qtxmlpatterns:
> > > /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0
> > > -alpha1
> > +gitAUTOINC+94136d4280
> > -r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
> > > is owned by uid 1000, which is the same as the user running
> > > bitbake.
> > > This may be due to host contamination [host-user-contaminated]
> > > 
> > > I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few
> > > recipes
> > > set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
> > > 
> > > Help appreciated
> > > 
> > > Andreas
> > 
> > I see this also in my builds. The warnings clutter the build output
> > in a
> > way that makes the warnings mostly useless. Who will spot the one
> > important new warning in the hundreds of host-user-contaminated
> > ones?
> > A fresh build of core-image-minimal today gave me 54 of these
> > warnings.
> > All but one (glibc-locale) complaining on source files.
> > 
> > I checked a few recipes and most of them were not even using a
> > custom
> > do_install but autotools generated 'make install' with something
> > like
> > 'cp -p src/* dest/' or so.
> > 
> 
> Yes, this is the most common case. Usage of cp -a or cp -p means the
> build
> ownership is retained, and no chown is run to fix it.
> 
> 
> > Even if I know how to do it I think we should not patch upstream
> > sources
> > to suppress a warning introduced by the downstream build system
> > with
> > loads of false positives and then have to maintain the patches as
> > upstream is progressing.
> > 
> 
> Either we're calling the upstream buildsystem and not running cp
> directly,
> in which case it's a bug in the upstream buildsystem, since make
> install
> will result in non-deterministic behavior in the ownership of the
> installed
> files, or it's a cp -a case, which doesn't require altering upstream
> with a
> patch at all, only recipe modification.
> 
> 
> > I haven't looked into how one does it but I'm inclined to switch of
> > the
> > warning globally, e.g. in local.conf.
> 
> 
> Blindly disabling them will just result in ignoring a problem. Files
> in the
> target filesystem are owned by your build user, who most likely
> doesn't
> even exist on target.

Don't you get me wrong, fixing the issues are a good plan. My point is
that currently there are so many [host-user-contaminated] warnings,
more or less all with -dbg packages, that I fear to overlook a warning
which is more likely to indicate a bug that is going haunt me.

Regards
Max

Re: Lots of [host-user-contaminated] warning

[Phil Reid]

On 17/11/2015 4:46 PM, Andreas Müller wrote:
> Hi,
>
> this bugs me for a while and I wonder if I am again the only one
> facing this: I get floods of warnings for sourcecode files as
>
> WARNING: QA Issue: qtserialport:
> /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: qtx11extras:
> /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: qtxmlpatterns:
> /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
>
> I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
> set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
>
> Help appreciated
>
> Andreas
>
I'm seeing similar warnings as well.
I'm building from /home which I believe is susposed to be exempt from this test.
Not sure how to fix / avoid the problem.


-- 
Regards
Phil Reid

Re: Lots of [host-user-contaminated] warning

[Mike Looijmans]

On 17-11-15 09:46, Andreas Müller wrote:
> Hi,
>
> this bugs me for a while and I wonder if I am again the only one
> facing this: I get floods of warnings for sourcecode files as
>
> WARNING: QA Issue: qtserialport:
> /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: qtx11extras:
> /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
> WARNING: QA Issue: qtxmlpatterns:
> /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
> is owned by uid 1000, which is the same as the user running bitbake.
> This may be due to host contamination [host-user-contaminated]
>
> I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
> set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
>
> Help appreciated

I got rid of these messages by doing the following replacements in do_install 
and package install scripts:

Instead of "cp -r -p ..." use "cp -r --preserve=mode,links ..."
Instead of "cp -a ..." use "cp -R --no-dereference --preserve=mode,links ..."

This fixes these QA warnings in a more structured way than running a blunt 
"chown root:root ..."




Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

Re: Lots of [host-user-contaminated] warning

[Phil Reid]

On 18/01/2016 4:02 PM, Mike Looijmans wrote:
> On 17-11-15 09:46, Andreas Müller wrote:
>> Hi,
>>
>> this bugs me for a while and I wonder if I am again the only one
>> facing this: I get floods of warnings for sourcecode files as
>>
>> WARNING: QA Issue: qtserialport:
>> /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
>> is owned by uid 1000, which is the same as the user running bitbake.
>> This may be due to host contamination [host-user-contaminated]
>> WARNING: QA Issue: qtx11extras:
>> /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
>> is owned by uid 1000, which is the same as the user running bitbake.
>> This may be due to host contamination [host-user-contaminated]
>> WARNING: QA Issue: qtxmlpatterns:
>> /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
>> is owned by uid 1000, which is the same as the user running bitbake.
>> This may be due to host contamination [host-user-contaminated]
>>
>> I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
>> set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
>>
>> Help appreciated
>
> I got rid of these messages by doing the following replacements in do_install and package install scripts:
>
> Instead of "cp -r -p ..." use "cp -r --preserve=mode,links ..."
> Instead of "cp -a ..." use "cp -R --no-dereference --preserve=mode,links ..."
>
> This fixes these QA warnings in a more structured way than running a blunt "chown root:root ..."
>
>
>

G'day Mike,

Was this on a recipe by recipe basis?
I've reported the following bug at https://bugzilla.yoctoproject.org/show_bug.cgi?id=8939
But told we need to update the recipes on a recipe by recipe.
I'm still learning bitbake, yocto and angstron relationships.
So far I at a loss on where to look.
eg: getting a problem with glib-2.22 which I can only find references to in openembedded-core.
But they suggest problem is in on of my extra layers.



-- 
Regards
Phil Reid