On Tue, Jun 7, 2016 at 7:55 PM, Gary Thomas wrote:
> I'm seeing a lot of these:
> NOTE: /local/poky-cutting-edge/meta-xyz/.../some-pkg_2.38.0.bb:
> base_contains is deprecated, please use bb.utils.contains instead.
>
> This is all well and good and I'll clean them up as I
I'm seeing a lot of these:
NOTE: /local/poky-cutting-edge/meta-xyz/.../some-pkg_2.38.0.bb: base_contains is deprecated, please use
bb.utils.contains instead.
This is all well and good and I'll clean them up as I go. That
said, why is the same NOTE printed [at least] twice for every recipe
On Tue, Nov 17, 2015 at 8:33 AM, Gary Thomas wrote:
> When I run bitbake using layers that are not GIT repos, I'm
> now getting a lot of messages like this:
> fatal: Not a git repository (or any parent up to mount point /raid)
> Stopping at filesystem boundary
When I run bitbake using layers that are not GIT repos, I'm
now getting a lot of messages like this:
fatal: Not a git repository (or any parent up to mount point /raid)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
This seems to be new (I've built from such trees
On Tue, Nov 17, 2015 at 11:02 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> On Tuesday 17 November 2015 08:39:55 Christopher Larson wrote:
> > On Tue, Nov 17, 2015 at 8:33 AM, Gary Thomas wrote:
> > > When I run bitbake using layers that are not GIT repos, I'm
>
On Tuesday 17 November 2015 08:39:55 Christopher Larson wrote:
> On Tue, Nov 17, 2015 at 8:33 AM, Gary Thomas wrote:
> > When I run bitbake using layers that are not GIT repos, I'm
> >
> > now getting a lot of messages like this:
> > fatal: Not a git repository (or any
On 17 November 2015 at 18:02, Paul Eggleton
wrote:
> I already sent a patch for this, it hasn't been applied yet:
>
> http://patchwork.openembedded.org/patch/107081/
>
It's in MUT, so should be in master fairly shortly.
Ross
--