All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] beaglebone-getting-started: Use cp options to not alter file mode
Date: Fri, 12 Oct 2018 16:31:49 -0400	[thread overview]
Message-ID: <20181012203149.GW19188@beryl> (raw)
In-Reply-To: <CAMKF1spE0fJTErUNg=ifQx9s2T-UybjAL++GFwZM+Pyi77pJwg@mail.gmail.com>

On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko <denys@ti.com> wrote:
> >
> > Are you still trying to do world builds? :)
> >
> 
> yes. with the patches I send in this week meta-ti seems to behave in
> multi-BSP setup
> I will soon add it to bblayers.conf for Yoe distro and it will start
> testing on meta-openembedded CI builds, atleast for not nosing other
> BSPs, I dont have infra to do world build for all the machines
> 
> but if you were to pick Yoe distro and run with it for machines you
> are interested in
> that would be awesome.
> 
> See. https://github.com/YoeDistro/yoe-distro, everyone having interesting boards
> is welcome to run world builds using that and report problems.

I can probably add it to my CI loop as well - I already do extensive builds 
and tests on Arago, Poky and distroless.


> > Most of the places with this QA warning that are part of our builds were fixed
> > before, but there are some outdated recipes like this one which were left out.
> >
> >
> > On Fri, Oct 12, 2018 at 12:50:00PM -0700, Khem Raj wrote:
> > > Fixes do_package_qa warnings
> > > <FILE> is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > ---
> > >  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > index 603a01a7..6c61a4e9 100644
> > > --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > @@ -14,7 +14,7 @@ S = "${WORKDIR}/git"
> > >
> > >  do_install() {
> > >       install -d ${D}${datadir}/${PN}
> > > -     cp -a ${S}/* ${D}${datadir}/${PN}
> > > +     cp -R --no-dereference --preserve=mode,links ${S}/* ${D}${datadir}/${PN}
> > >  }
> > >
> > >  FILES_${PN} += "${datadir}/${PN}"
> > > --
> > > 2.19.1
> > >
> > > --
> > > _______________________________________________
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti


  reply	other threads:[~2018-10-12 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 19:50 [PATCH] beaglebone-getting-started: Use cp options to not alter file mode Khem Raj
2018-10-12 19:58 ` Denys Dmytriyenko
2018-10-12 20:01   ` Khem Raj
2018-10-12 20:31     ` Denys Dmytriyenko [this message]
2018-10-12 20:34       ` Khem Raj
2018-10-12 20:37         ` Denys Dmytriyenko
2018-10-12 20:49           ` Khem Raj
2018-10-12 21:01             ` Denys Dmytriyenko
2018-10-12 21:14               ` Khem Raj
2018-10-12 21:20                 ` Denys Dmytriyenko

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=20181012203149.GW19188@beryl \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.