Re: [yocto] New warning

[Christopher Larson]

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 go.  That
> said, why is the same NOTE printed [at least] twice for every recipe
> even when the file contains 'base_contains' only once?
>

I haven't checked the code, but the most likely explanation is the error is
a parse or expansion time one, and bitbake parses the recipe anew when
running each task, after the up front parse which is used to generate the
runqueue. *shrug*. It's a downside of showing messages in anything but task
execution context.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New warning(s)

[Christopher Larson]

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 (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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New warning(s)

[Christopher Larson]

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
> > >
> > > 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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 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  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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] New warning(s)

[Burton, Ross]

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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto