New warning(s)
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?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 6 lines · 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_FILESYSTEMnot
set).
Quoted 7 lines
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.
Signature · 5 lines
Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
Quoted 14 lines · On Tuesday 17 November 2015 08:39:55 Christopher Larson wrote:
Quoted 13 lines · 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_FILESYSTEMnotset).
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)
Quoted 6 lines
Quoted 1 line
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 themetadata_scmfunctions were reworked recently.
I already sent a patch for this, it hasn't been applied yet:
http://patchwork.openembedded.org/patch/107081/
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 19 lines · Paul Eggleton
Quoted 14 lines · On Tuesday 17 November 2015 08:39:55 Christopher Larson wrote:
Quoted 13 lines · 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_FILESYSTEMnotset).
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)
Quoted 4 lines
Quoted 1 line
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
Quoted 7 lines
to
Quoted 2 lines
me like an accidental loss of the stderr capture/suppression when the
metadata_scmfunctions were reworked recently.I already sent a patch for this, it hasn't been applied yet:
Ah, excellent. Thanks.
Signature · 5 lines
Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
Quoted 4 lines · Paul Eggleton
I already sent a patch for this, it hasn't been applied yet:
It's in MUT, so should be in master fairly shortly.
Ross