Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <kergoth@gmail.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Add checks for "host user contamination"
Date: Tue, 01 Sep 2015 08:52:20 +0100	[thread overview]
Message-ID: <1441093940.26554.57.camel@linuxfoundation.org> (raw)
In-Reply-To: <1441093853.26554.56.camel@linuxfoundation.org>

On Tue, 2015-09-01 at 08:50 +0100, Richard Purdie wrote:
> On Mon, 2015-08-24 at 15:19 -0700, Christopher Larson wrote:
> > From: Christopher Larson <chris_larson@mentor.com>
> > 
> > This adds a QA test, as well as a rootfs_ function for use in
> > ROOTFS_POSTPROCESS_COMMAND, to warn/error when paths are owned by the same
> > user/group as the user running bitbake. This is useful to catch stuff which is
> > written outside of pseudo's control, for example.
> > 
> > The following changes since commit c38acd720b3f6ffbeb544063692eb471dada8593:
> > 
> >   binconfig-disabled: write an message to stderr to help confused developers (2015-08-19 17:57:58 +0100)
> > 
> > are available in the git repository at:
> > 
> >   git://github.com/kergoth/openembedded-core host-user-contaminated
> >   https://github.com/kergoth/openembedded-core/tree/host-user-contaminated
> > 
> > Christopher Larson (3):
> >   insane.bbclass: handle tests which need fakeroot
> >   insane.bbclass: add host-user-contaminated test
> >   image.bbclass: add rootfs_check_host_user_contaminated
> 
> On the autobuilder we found:
> 
> http://errors.yoctoproject.org/Errors/Details/16318/
> 
> which looks like a race against the packaging code and the creation of
> package manager files. Not sure why we don't see this in other cases...

Also http://errors.yoctoproject.org/Errors/Details/16310/ which looks
like the same issue (racing dpkg rather than opkg).

Cheers,

Richard



  reply	other threads:[~2015-09-01  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 22:19 [PATCH 0/3] Add checks for "host user contamination" Christopher Larson
2015-08-24 22:19 ` [PATCH 1/3] insane.bbclass: handle tests which need fakeroot Christopher Larson
2015-08-24 22:19 ` [PATCH 2/3] insane.bbclass: add host-user-contaminated test Christopher Larson
2015-08-26  8:44   ` Joshua Lock
2015-08-26 11:01     ` Burton, Ross
2015-08-26 14:19       ` Christopher Larson
2015-08-26 14:20         ` Christopher Larson
2015-08-26 14:24           ` Joshua Lock
2015-08-24 22:19 ` [PATCH 3/3] image.bbclass: add rootfs_check_host_user_contaminated Christopher Larson
2015-09-01  7:50 ` [PATCH 0/3] Add checks for "host user contamination" Richard Purdie
2015-09-01  7:52   ` Richard Purdie [this message]
2015-09-01 15:05     ` Christopher Larson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1441093940.26554.57.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=chris_larson@mentor.com \
    --cc=kergoth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox