From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Paulo Neves <ptsneves@gmail.com>,
Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: ROOTFS_RPM_DEBUG undocumented
Date: Thu, 3 May 2018 17:21:52 +0300 [thread overview]
Message-ID: <db9f3d8e-d24c-bf12-db37-084487e747de@linux.intel.com> (raw)
In-Reply-To: <50b98492ad0d40a0b8f32933c371125f@XBOX02.axis.com>
On 05/03/2018 04:37 PM, Peter Kjellerstedt wrote:
>>> # Have dnf always print in verbose mode and print the output to
>>> bb.debug instead of bb.note.
>>
>> I think this is the best solution actually.
>
> I disagree with changing bb.note to bb.debug for this. It is very good
> to be able to look in log.do_rootfs to see what dnf has done (we have
> ROOTFS_RPM_DEBUG set by default). Changing the output to debug level
> would mean having to run bitbake with -D, which is anything but
> desirable.
If I'm reading the bitbake --help right, bb.debug (and bb.note) are
always written to the log; setting -D level or -v only affects what is
printed on stdout.
Alex
next prev parent reply other threads:[~2018-05-03 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 10:42 ROOTFS_RPM_DEBUG undocumented Paulo Neves
2018-05-03 13:03 ` Alexander Kanavin
2018-05-03 13:37 ` Peter Kjellerstedt
2018-05-03 14:21 ` Alexander Kanavin [this message]
2018-05-04 12:42 ` Paulo Neves
2018-05-04 12:41 ` Alexander Kanavin
2018-05-04 12:43 ` Alexander Kanavin
2018-05-04 12:50 ` Scott Rifenbark
2018-05-04 12:45 ` Alexander Kanavin
2018-05-04 12:55 ` Paulo Neves
2018-05-07 9:03 ` Mirza Krak
2018-05-07 10:12 ` Alexander Kanavin
2018-05-08 9:33 ` Peter Kjellerstedt
2018-05-08 10:29 ` Alexander Kanavin
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=db9f3d8e-d24c-bf12-db37-084487e747de@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=peter.kjellerstedt@axis.com \
--cc=ptsneves@gmail.com \
--cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.