From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: dbus-test no longer built for dbus-ptest after last bitbake changes
Date: Tue, 21 Jul 2015 10:44:20 +0100 [thread overview]
Message-ID: <1437471860.821.63.camel@linuxfoundation.org> (raw)
In-Reply-To: <20150714142140.GC2184@jama>
On Tue, 2015-07-14 at 16:21 +0200, Martin Jansa wrote:
> I'm not 100% sure it's related to recent bitbake variable expansion
> changes, but my recent builds are failing with errors about
> dbus-ptest cannot be installed because dbus-test-ptest doesn't exist
>
> ERROR:
> Collected errors:
>
> * satisfy_dependencies_for: Cannot satisfy the following dependencies
> * for dbus-ptest:
>
> * dbus-test-ptest *
>
> * opkg_install_cmd: Cannot install package dbus-ptest.
>
> It's using a bit strange construct to add it to RDEPENDS:
> meta/recipes-core/dbus/dbus.inc:RDEPENDS_dbus-ptest_class-target =
> "dbus-test-ptest"
>
> but checking cooker log shows that dbus-test
> (meta/recipes-core/dbus/dbus-test_1.8.18.bb) wasn't built at all, only
> dbus-test message is from opkg error and this QA error from dbus itself:
>
> NOTE: recipe dbus-1.8.18-r0: task do_package_write_ipk: Started
> WARNING: QA Issue: dbus-ptest rdepends on dbus-test-ptest, but it isn't
> a build dependency? [build-deps]
>
> Any ideas?
I've confirmed this is a bug in the bitbake data store changes. The fix
is to replace a copy.copy() with a copy.deepcopy(). I'll sort out
patches as soon as I can although I'm travelling a bit this week. Also
need to write a testcase for it.
Cheers,
Richard
prev parent reply other threads:[~2015-07-21 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 14:21 dbus-test no longer built for dbus-ptest after last bitbake changes Martin Jansa
2015-07-16 21:29 ` Martin Jansa
2015-07-16 22:22 ` Burton, Ross
2015-07-17 12:01 ` Richard Purdie
2015-07-21 9:11 ` Richard Purdie
2015-07-16 21:39 ` Richard Purdie
2015-07-21 9:44 ` 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=1437471860.821.63.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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