On Tue, Sep 1, 2015 at 12:52 AM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote:
> 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_lar...@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). Ah, indeed, sorry about that, I must have gotten lucky with our builds thus far. I'll re-submit, ignoring ENOENT. -- Christopher Larson kergoth at gmail dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core