From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
Peter Kjellerstedt <pkj@axis.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: "openembedded-commits@lists.openembedded.org"
<openembedded-commits@lists.openembedded.org>
Subject: Re: [oe-commits] [openembedded-core] 01/02: package.bbclass: Restore functionality to detect RPM dependencies
Date: Mon, 21 Aug 2017 22:08:23 +0100 [thread overview]
Message-ID: <1503349703.32591.72.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQfbEAVhPbPeOi=vfMcjds2DMGtMGz256gode6+2NdzMug@mail.gmail.com>
On Mon, 2017-08-21 at 11:00 +0200, Martin Jansa wrote:
> This seems to find a many more missed dependencies which is good
> thing.
>
> There is +- 20 failures found in meta-oe recipes and there is still
> at least one in oe-core:
>
> ERROR: nativesdk-libcheck-0.10.0-r0 do_package_qa: QA Issue:
> /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/checkmk
> contained in package nativesdk-libcheck requires /usr/local/oecore-
> x86_64/sysroots/x86_64-oesdk-linux/usr/bin/gawk, but no providers
> found in RDEPENDS_nativesdk-libcheck? [file-rdeps]
>
> I wonder why this one wasn't catched by oe-core autobuilder.
At a guess, nativesdk are excluded from world so nothing in OE-Core
likely depends on nativesdk-libcheck. Thanks for the patch, you beat me
to it!
Cheers,
Richard
prev parent reply other threads:[~2017-08-21 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <150290188985.5203.15184613586486279186@git.openembedded.org>
[not found] ` <20170816164450.1447E236566@git.openembedded.org>
2017-08-21 9:00 ` [oe-commits] [openembedded-core] 01/02: package.bbclass: Restore functionality to detect RPM dependencies Martin Jansa
2017-08-21 20:56 ` [PATCH] libcheck: fix file-rdeps QA issue Martin Jansa
2017-08-21 21:08 ` 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=1503349703.32591.72.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pkj@axis.com \
/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