From: Craig McQueen <craig.mcqueen@innerrange.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Missing RDEPENDS on libldb, libtevent
Date: Fri, 7 Dec 2018 03:15:14 +0000 [thread overview]
Message-ID: <c4f487118ad847bda609a64302287ee4@innerrange.com> (raw)
I am doing Yocto builds with Yocto sumo, and using the meta-oe layer.
I recently updated Yocto poky from eebbc00b to 64a257fa, and updated meta-oe from 2bb21ef2 to 8760facb. After that, I found I got build errors:
ERROR: libldb-1.3.1-r0 do_package_qa: QA Issue: /usr/lib/python2.7/site-packages/ldb.so contained in package pyldb requires libldb.so.1(LDB_0.9.10), but no providers found in RDEPENDS_pyldb? [file-rdeps]
ERROR: libldb-1.3.1-r0 do_package_qa: QA Issue: /usr/lib/python2.7/site-packages/ldb.so contained in package pyldb requires libldb.so.1, but no providers found in RDEPENDS_pyldb? [file-rdeps]
...
ERROR: libldb-1.3.1-r0 do_package_qa: QA Issue: /usr/lib/libldb.so.1.3.1 contained in package libldb requires libtevent.so.0(TEVENT_0.9.9), but no providers found in RDEPENDS_libldb? [file-rdeps]
ERROR: libldb-1.3.1-r0 do_package_qa: QA Issue: /usr/lib/libldb.so.1.3.1 contained in package libldb requires libtevent.so.0, but no providers found in RDEPENDS_libldb? [file-rdeps]
...
ERROR: libtevent-0.9.36-r0 do_package_qa: QA Issue: /usr/lib/python2.7/site-packages/_tevent.so contained in package python-tevent requires libtevent.so.0(TEVENT_0.9.9), but no providers found in RDEPENDS_python-tevent? [file-rdeps]
ERROR: libtevent-0.9.36-r0 do_package_qa: QA Issue: /usr/lib/python2.7/site-packages/_tevent.so contained in package python-tevent requires libtevent.so.0, but no providers found in RDEPENDS_python-tevent? [file-rdeps]
I'm not sure what changed to make these errors appear, but I have added RDEPENDS lines in bbappend as a work-around for now.
--
Craig McQueen
reply other threads:[~2018-12-07 3:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c4f487118ad847bda609a64302287ee4@innerrange.com \
--to=craig.mcqueen@innerrange.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.