From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Stéphane Veyret" <sveyret@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Questions on multiconfig
Date: Sat, 05 Aug 2023 16:54:32 +0100 [thread overview]
Message-ID: <2a629a98608740b32716d596ed0b4bc8a4892cab.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAFs+hh7nisDjEG2C0cF9i2gR+xVhtyBGSCr2v4xWRgQ1Cz-5Lw@mail.gmail.com>
On Sat, 2023-08-05 at 16:04 +0200, Stéphane Veyret wrote:
> > First of all, I am spammed with messages like:
> >
> > NOTE: Deferred task
> > mc:initramfs:/home/stephane/Developpements/yocto/sources/poky/meta/
> > recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_package_qa now
> > buildable
> > NOTE: Deferred task
> > mc:initramfs:virtual:native:/home/stephane/Developpements/yocto/sou
> > rces/poky/meta/recipes-
> > devtools/opkg/opkg_0.6.1.bb:do_populate_sysroot now buildable
> >
>
>
> I am still spammed by all these messages. I’d like to understand why.
> And if possible, I’d also like to mute the messages I’ve seen and
> decided they are not important. It doesn’t seem possible, so I may
> send a patch in the future for that case.
https://git.yoctoproject.org/poky/commit/bitbake?id=ebb8b39463cef3c3d0f90f054c433b2f5256cb1a
It is also possible to write specific log configuration files to
control the different messages.
That said, see the discussion on the bitbake-devel list about this
patch and why merging it will probably prevent us debugging some kinds
of build issues in future :/.
Cheers,
Richard
prev parent reply other threads:[~2023-08-05 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17775879C46AA70D.29484@lists.yoctoproject.org>
2023-08-05 14:04 ` [yocto] Questions on multiconfig Stéphane Veyret
2023-08-05 15:54 ` Richard Purdie [this message]
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=2a629a98608740b32716d596ed0b4bc8a4892cab.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=sveyret@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox