All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: dbus-test no longer built for dbus-ptest after last bitbake changes
Date: Tue, 14 Jul 2015 16:21:40 +0200	[thread overview]
Message-ID: <20150714142140.GC2184@jama> (raw)

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

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?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2015-07-14 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 14:21 Martin Jansa [this message]
2015-07-16 21:29 ` dbus-test no longer built for dbus-ptest after last bitbake changes 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

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=20150714142140.GC2184@jama \
    --to=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 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.