New warning(s)

New warning(s)

[Gary Thomas]

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 many times
before with no such messages) and it hardly seems "fatal".
The messages apparently are coming from 'git' (I tested with
git version 1.9.1 and 1.7.11)

Why the change?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: New warning(s)

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

On Tue, Nov 17, 2015 at 8:33 AM, Gary Thomas <gary@mlbassoc.com> 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 (GIT_DISCOVERY_ACROSS_FILESYSTEM not
> set).
>
> This seems to be new (I've built from such trees many times
> before with no such messages) and it hardly seems "fatal".
> The messages apparently are coming from 'git' (I tested with
> git version 1.9.1 and 1.7.11)
>
> Why the change?
>

I believe we need https://github.com/kergoth/meta-mentor/commit/2125799
applied to oe-core, haven't had a chance to submit it yet, but it looked to
me like an accidental loss of the stderr capture/suppression when the
metadata_scm functions were reworked recently.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 1581 bytes --]

Re: New warning(s)

[Paul Eggleton]

On Tuesday 17 November 2015 08:39:55 Christopher Larson wrote:
> On Tue, Nov 17, 2015 at 8:33 AM, Gary Thomas <gary@mlbassoc.com> 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 (GIT_DISCOVERY_ACROSS_FILESYSTEM not
> > 
> > set).
> > 
> > This seems to be new (I've built from such trees many times
> > before with no such messages) and it hardly seems "fatal".
> > The messages apparently are coming from 'git' (I tested with
> > git version 1.9.1 and 1.7.11)
> > 
> > Why the change?
> 
> I believe we need https://github.com/kergoth/meta-mentor/commit/2125799
> applied to oe-core, haven't had a chance to submit it yet, but it looked to
> me like an accidental loss of the stderr capture/suppression when the
> metadata_scm functions were reworked recently.

I already sent a patch for this, it hasn't been applied yet:

http://patchwork.openembedded.org/patch/107081/

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: New warning(s)

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

On Tue, Nov 17, 2015 at 11:02 AM, Paul Eggleton <
paul.eggleton@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 <gary@mlbassoc.com> 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 (GIT_DISCOVERY_ACROSS_FILESYSTEM not
> > >
> > > set).
> > >
> > > This seems to be new (I've built from such trees many times
> > > before with no such messages) and it hardly seems "fatal".
> > > The messages apparently are coming from 'git' (I tested with
> > > git version 1.9.1 and 1.7.11)
> > >
> > > Why the change?
> >
> > I believe we need https://github.com/kergoth/meta-mentor/commit/2125799
> > applied to oe-core, haven't had a chance to submit it yet, but it looked
> to
> > me like an accidental loss of the stderr capture/suppression when the
> > metadata_scm functions were reworked recently.
>
> I already sent a patch for this, it hasn't been applied yet:
>
> http://patchwork.openembedded.org/patch/107081/


Ah, excellent. Thanks.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 2219 bytes --]

Re: New warning(s)

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 271 bytes --]

On 17 November 2015 at 18:02, Paul Eggleton <paul.eggleton@linux.intel.com>
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

[-- Attachment #2: Type: text/html, Size: 790 bytes --]