[dss-merge-requests] Build failed in Jenkins: yocto #3190

[dS Jenkins]

See <http://dsjenkins.cloudapp.net/jenkins/job/yocto/3190/display/redirect?page=changes>

Changes:

[andreas.fenkart] reflash_rootfs: dsd-4437: suppress rescue upgrade on 5.1.7 kernel

------------------------------------------
[...truncated 66.50 KB...]
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/XmlRpcCpp.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/xml.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/param_list.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/outcome.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/value.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/curl.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/transport_config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/abyss.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/registry.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/base.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/env_wrap.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/transport.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/base.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/server_pstream.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/packetsocket.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/girmem.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/oldcppwrapper.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/server.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/base_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/client_simple.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/client_transport.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/abyss_unixsock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/girerr.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/xml.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/client.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/server_abyss.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/server_cgi.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/client.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/server_abyss.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/cpp/blddir/include/xmlrpc-c/timeout.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/srcdir/lib/expat/xmlparse/xmlparse.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/srcdir/lib/util/include/mallocvar.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/srcdir/lib/util/include/bool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/srcdir/lib/util/include/stdargx.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/transport_config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/abyss.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/client_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/transport.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/base.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/lock_platform.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/server.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/base_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/time_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/string_number.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/abyss_unixsock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/inttypes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/lock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/client.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/server_abyss.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/src/blddir/include/xmlrpc-c/xmlparser.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/client_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/transport.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/base.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/lock_platform.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/time_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/select_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/lock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/client.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/include/xmlrpc-c/lock_pthread.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/AbyssEnvironment.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/AbyssChanSwitch.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/AbyssServer.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/abyss.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/AbyssServer.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/AbyssEnvironment.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/abyss_unixsock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/inttypes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/girerr.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss++/blddir/include/xmlrpc-c/AbyssChanSwitch.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/socket_unix.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/token.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/conn.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/handler.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/data.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/date.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/handler.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/conn.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/init.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/session.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/session.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/thread.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/file.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/data.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/socket.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/http.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/server.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/http.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/channel.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/socket.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/channel.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/socket_unix.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/response.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/trace.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/server.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/chanswitch.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/date.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/trace.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/file.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/thread_pthread.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/conf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/chanswitch.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/token.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/abyss.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/sleep_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/lock_platform.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/time_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/abyss_unixsock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/inttypes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/lock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/include/xmlrpc-c/base64_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/lib/util/include/mallocvar.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/abyss/src/srcdir/lib/util/include/bool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmlrole.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmlrole.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmltok.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmltok_ns.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/nametab.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmltok_impl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmltok_impl.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/xmltok.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmltok/srcdir/lib/util/include/bool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/xmlparse.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/xmlparse.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/srcdir/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/srcdir/lib/expat/xmltok/xmlrole.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/srcdir/lib/expat/xmltok/xmltok.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/srcdir/lib/util/include/mallocvar.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/expat/xmlparse/srcdir/lib/util/include/bool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/utf8.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/select.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/make_printable.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/memblock.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/sleep.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/time.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/lock_platform.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/string_number.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/asprintf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/lock_none.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/error.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/base64.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/lock_pthread.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil/srcdir/lib/util/include/bool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/girerr.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/Lock.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/girmem.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/env_wrap.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/base64.cpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/env_wrap.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/string_int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/girmem.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/lock_platform.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/base64.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/Lock.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/lock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/libutil++/blddir/include/xmlrpc-c/girerr.hpp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/curl_transport/curlmulti.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/curl_transport/xmlrpc_curl_transport.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/curl_transport/curltransaction.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/curl_transport/curltransaction.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/curl_transport/curlmulti.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/src/debug/xmlrpc-c/1.39.12-r2/xmlrpc-c-1.39.12/lib/curl_transport/srcdir/lib/util/include/bool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_xmltok.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_util.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_client.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_packetsocket.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server_cgi++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server_abyss.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_xmlparse.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server_pstream++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_client++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_abyss.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server_cgi.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_util++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_abyss++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server_abyss++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_server.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c-dbg/usr/lib/.debug/libxmlrpc_cpp.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe ds485p-git-r5: task do_package_write_ipk: Succeeded
WARNING: xmlrpc-c-1.39.12-r2 do_package_qa: QA Issue: xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_abyss.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_pstream++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_xmltok.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_util.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_cgi++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_abyss++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_cgi.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_client.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_packetsocket.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_cpp.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_util++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_client++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_cgi++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_abyss.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_util.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_xmlparse.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_pstream++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_xmlparse.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_client++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_abyss.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_cgi.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_client.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_util++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_packetsocket.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_abyss++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_abyss++.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server.so.3.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_abyss++.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_cpp.so.8.39 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_server_abyss.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
xmlrpc-c: /xmlrpc-c/usr/lib/libxmlrpc_xmltok.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_qa: Succeeded
NOTE: recipe libsolv-0.6.33-r0: task do_compile: Succeeded
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_write_ipk: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Succeeded
NOTE: recipe libpagekite-git-r4: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 4022 tasks of which 4005 didn't need to be rerun and 1 failed.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.

Summary: 1 task failed:
  /home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install
Summary: There were 6 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

bitbake returned 1, manual interaction required!

Build step 'Execute shell' marked build as failure
Not sending mail to unregistered user Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user jean.visagie at digitalstrom.com
Not sending mail to unregistered user jin at developer.digitalstrom.org