All of lore.kernel.org
 help / color / mirror / Atom feed
* OE recipe tree quality
@ 2010-07-29  8:50 Frans Meulenbroeks
  2010-07-29  9:42 ` Thomas Zimmermann
  2010-07-29  9:45 ` Koen Kooi
  0 siblings, 2 replies; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-29  8:50 UTC (permalink / raw)
  To: openembedded-devel

Dear all,

Given the discussions on quality that sometimes pop up (and also triggered
by Robert's message), I decided to kick off a bitbake -k world.
Below are some initial findings. I would like to use this as a starter to
kickoff the discusson on quality and what to do with broken stuff.
And also I hope that people who feel attached to a recipe mentioned below
will take action.

My setting:
local.conf:
IMAGE_LINGUAS = ""
ENABLE_BINARY_LOCALE_GENERATION = "0"

MACHINE = "beagleboard"
DISTRO = "angstrom-2008.1"

EXTRA_IMAGECMD_jffs2 = "--pad --eraseblock=0x20000"
MKUBIFS_ARGS = "-m 2048 -e 129024 -c 1024"

IMAGE_FSTYPES = "tar squashfs ubifs jffs2"
IMAGE_KEEPROOTFS = "1"
OE_ALLOW_INSECURE_DOWNLOADS = "yes"

I opted for angstromg and beagleboard as I feel this is the most often build
configuration, so it should have the least issues.
host is ubuntu 10.04 on 64 bit. tree is oe dev git head (as of jul 29)

All results are not in yet (there are 71047 taksks, I am at 159 :-)
However the parsing already gave some interesting output.
I've ordered them somehwat:

Nothing PROVIDES errors
===================

ERROR: Nothing PROVIDES 'etk'
ERROR: Nothing PROVIDES 'sugar-web-activity'
ERROR: Nothing PROVIDES 'hildon-lgpl' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbDEPENDS
on or otherwise requires it)
ERROR: Nothing PROVIDES 'hildon-base-lib'
ERROR: Nothing PROVIDES 'hildon-libs'
ERROR: Nothing PROVIDES 'python-etk' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-settings_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbDEPENDS
on or otherwise requires it)
ERROR: Nothing PROVIDES 'gconf-osso'
ERROR: Nothing PROVIDES 'epsilon'
ERROR: Nothing PROVIDES 'libmsip0'
ERROR: Nothing PROVIDES 'libmikey0'
ERROR: Nothing PROVIDES 'xmu'
ERROR: Nothing PROVIDES 'ipkg' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bb,
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbDEPENDS
on or otherwise requires it)
ERROR: Nothing PROVIDES 'evas-fb'
ERROR: Nothing PROVIDES 'ecore-fb'
ERROR: Nothing PROVIDES 'esmart-fb'
ERROR: Nothing PROVIDES 'imlib2-fb'
ERROR: Nothing PROVIDES 'efl++-fb'
ERROR: Nothing PROVIDES 'codec-engine'
ERROR: Nothing PROVIDES 'sword'
ERROR: Nothing PROVIDES 'clutter-0.6'
ERROR: Nothing PROVIDES 'hildon-fm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbDEPENDS
on or otherwise requires it)
ERROR: Nothing PROVIDES 'libgsmd-lips'
ERROR: Nothing PROVIDES 'libmnetutil0'
ERROR: Nothing PROVIDES 'xdamage'
ERROR: Nothing PROVIDES 'etk-native'
ERROR: Nothing PROVIDES 'bluez-libs-3.36'

Apparently we have some issues here. I am not really a user of any of this
package and for most of them I have no idea what they do (so I have not
really too much interest to burn spare time to fix them) . Some of these are
apparently quite old too.
(I've checked out xdamage, this one is in the DEPENDS of
recipes/xvidcap/xvidcap.inc and that file has not been touched since the
packages -> recipes renaming).

Is anyone interested in a recipe that DEPENDS on these missing packages?
If so, what about some action to fix them.
If not, do we want to leave this crud around? Should we move to a
does-not-build dir? or delete?
Opinions wanted


Nothing RPROVIDES errors
====================

Big list,message continues after the list:
ERROR: Nothing RPROVIDES 'exhibit' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/e17/exhibit_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'om-locations' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-locations_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'om-settings' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'assassin' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin-thumbnail_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'assassin-thumbnail' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin-thumbnail_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-hmm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-itools' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-lightmediascanner' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-python-devel.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-pyreverse' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-snmplib' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-spyro' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-urwid' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-vmaps' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'twisted' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqt2' (but
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher.bb, /home/frans/workspace/tst/openembedded.git/recipes/xqt2/
xqt2_20060509.bb, /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-qpe.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqtlauncher' (but
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher.bb, /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-xqtlauncher.bb,
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher-blackbox-config.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gstreamer-ti-demo-script' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-gstreamer-ti.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-demo-x11' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libgles-omap3-demos' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bc-cat-omap3-module-tests' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'edje-player' (but
/home/frans/workspace/tst/openembedded.git/recipes/e17/edje-player_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'edje-editor' (but
/home/frans/workspace/tst/openembedded.git/recipes/e17/edje-editor_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'sugar-fructose' (but
/home/frans/workspace/tst/openembedded.git/recipes/sugar/sugar-fructose.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '|' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-base.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'e2fsprogs-uuidgen' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-base.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-todo-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/gpe-todo/
gpe-todo-hildon_0.55.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'evolve' (but
/home/frans/workspace/tst/openembedded.git/recipes/efl1/evolve_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-application-installer' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
osso-application-installer_1.0.03-1.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bluez-utils-compat' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-gpephone.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'diversity-radar' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
diversity-radar_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'lessertunjo' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
lessertunjo_0.0.10.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'omview' (but
/home/frans/workspace/tst/openembedded.git/recipes/omview/omview_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'epsilon-thumbd' (but
/home/frans/workspace/tst/openembedded.git/recipes/omview/omview_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bt950-cs' (but
/home/frans/workspace/tst/openembedded.git/recipes/bt950-cs/bt950-cs_0.1.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'minisip' (but
/home/frans/workspace/tst/openembedded.git/recipes/minisip/minisip_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'systemtap' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-systemtap.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-mamona-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-systemtap.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-applets' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-games' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-inputmethods' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-multimedia' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-emulators' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-applications' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-fonts' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-settings' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'aterm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-wm.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'dspgw-utils' (but
/home/frans/workspace/tst/openembedded.git/recipes/mamona/
mamona-sound-n800_0.1.0.bb,
/home/frans/workspace/tst/openembedded.git/recipes/mamona/
mamona-sound-n770_0.1.0.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ipkgorphan' (but
/home/frans/workspace/tst/openembedded.git/recipes/ipkg/ipkgorphan_0.0.1.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'openmoko-today' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-base/
openmoko-session_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'comic-reader' (but
/home/frans/workspace/tst/openembedded.git/recipes/comic-reader/
comic-reader_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-status-bar' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
hildon-status-bar_0.8.11-1.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'angstrom-bootmanager' (but
/home/frans/workspace/tst/openembedded.git/recipes/angstrom/
angstrom-bootmanager.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'fso-apm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-fso2-compliance.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'vlc-davinci' (but
/home/frans/workspace/tst/openembedded.git/recipes/vlc/vlc-davinci_0.8.6h.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal-cli' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal-apps' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'eflpp' (but
/home/frans/workspace/tst/openembedded.git/recipes/efl1/eflpp_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ipkg' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bb,
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-sdk-sbox-gpe' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/meta/
meta-toolchain-gpe-sbox.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-opie-bluetooth' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-opie-irda' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'outo' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-initscripts' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-thumbnail' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-lgpl' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libhildonbase' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libhildonwidgets' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-fm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-home' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-navigator' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-screenshot-tool' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-contacts-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-mini-browser-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bb,
/home/frans/workspace/tst/openembedded.git/recipes/gpe-mini-browser/
gpe-mini-browser-hildon_0.17.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'opie-dagger' (but
/home/frans/workspace/tst/openembedded.git/recipes/opie-dagger/
opie-dagger_1.2.4.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-opie-apps.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'clutter-gtk-0.6' (but
/home/frans/workspace/tst/openembedded.git/recipes/clutter/
clutter-gtk-0.6_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'udev-compat-wrapper' (but
/home/frans/workspace/tst/openembedded.git/recipes/udev/
udev-compat141_141.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'udev-compat141' (but
/home/frans/workspace/tst/openembedded.git/recipes/udev/
udev-compat141_141.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-openprotium' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_SSH_DAEMON}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_DEV_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_INIT_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_LOGIN_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-etk' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-settings_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-python-sharprom' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-minimal.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libmsgenabler2' (but
/home/frans/workspace/tst/openembedded.git/recipes/gpephone/
libmsgenabler2_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libmsip' (but
/home/frans/workspace/tst/openembedded.git/recipes/minisip/libmsip_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-openmoko-python-devel' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-python-devel.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'matchbox-panel-2-applets' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-base.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-xqtlERROR: Nothing RPROVIDES 'exhibit' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/e17/exhibit_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'om-locations' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-locations_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'om-settings' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'assassin' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin-thumbnail_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'assassin-thumbnail' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin-thumbnail_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-hmm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-itools' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-lightmediascanner' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-python-devel.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-pyreverse' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-snmplib' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-spyro' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-urwid' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-vmaps' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'twisted' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqt2' (but
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher.bb, /home/frans/workspace/tst/openembedded.git/recipes/xqt2/
xqt2_20060509.bb, /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-qpe.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqtlauncher' (but
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher.bb, /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-xqtlauncher.bb,
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher-blackbox-config.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gstreamer-ti-demo-script' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-gstreamer-ti.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-demo-x11' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libgles-omap3-demos' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bc-cat-omap3-module-tests' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'edje-player' (but
/home/frans/workspace/tst/openembedded.git/recipes/e17/edje-player_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'edje-editor' (but
/home/frans/workspace/tst/openembedded.git/recipes/e17/edje-editor_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'sugar-fructose' (but
/home/frans/workspace/tst/openembedded.git/recipes/sugar/sugar-fructose.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '|' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-base.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'e2fsprogs-uuidgen' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-base.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-todo-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/gpe-todo/
gpe-todo-hildon_0.55.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'evolve' (but
/home/frans/workspace/tst/openembedded.git/recipes/efl1/evolve_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-application-installer' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
osso-application-installer_1.0.03-1.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bluez-utils-compat' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-gpephone.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'diversity-radar' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
diversity-radar_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'lessertunjo' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
lessertunjo_0.0.10.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'omview' (but
/home/frans/workspace/tst/openembedded.git/recipes/omview/omview_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'epsilon-thumbd' (but
/home/frans/workspace/tst/openembedded.git/recipes/omview/omview_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bt950-cs' (but
/home/frans/workspace/tst/openembedded.git/recipes/bt950-cs/bt950-cs_0.1.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'minisip' (but
/home/frans/workspace/tst/openembedded.git/recipes/minisip/minisip_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'systemtap' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-systemtap.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-mamona-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-systemtap.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-applets' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-games' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-inputmethods' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-multimedia' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-emulators' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-applications' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-fonts' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-settings' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'aterm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-wm.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'dspgw-utils' (but
/home/frans/workspace/tst/openembedded.git/recipes/mamona/
mamona-sound-n800_0.1.0.bb,
/home/frans/workspace/tst/openembedded.git/recipes/mamona/
mamona-sound-n770_0.1.0.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ipkgorphan' (but
/home/frans/workspace/tst/openembedded.git/recipes/ipkg/ipkgorphan_0.0.1.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'openmoko-today' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-base/
openmoko-session_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'comic-reader' (but
/home/frans/workspace/tst/openembedded.git/recipes/comic-reader/
comic-reader_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-status-bar' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
hildon-status-bar_0.8.11-1.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'angstrom-bootmanager' (but
/home/frans/workspace/tst/openembedded.git/recipes/angstrom/
angstrom-bootmanager.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'fso-apm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-fso2-compliance.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'vlc-davinci' (but
/home/frans/workspace/tst/openembedded.git/recipes/vlc/vlc-davinci_0.8.6h.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal-cli' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal-apps' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'eflpp' (but
/home/frans/workspace/tst/openembedded.git/recipes/efl1/eflpp_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ipkg' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bb,
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-sdk-sbox-gpe' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/meta/
meta-toolchain-gpe-sbox.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-opie-bluetooth' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-opie-irda' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'outo' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-initscripts' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-thumbnail' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-lgpl' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libhildonbase' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libhildonwidgets' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-fm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-home' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-navigator' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-screenshot-tool' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-contacts-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-mini-browser-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bb,
/home/frans/workspace/tst/openembedded.git/recipes/gpe-mini-browser/
gpe-mini-browser-hildon_0.17.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'opie-dagger' (but
/home/frans/workspace/tst/openembedded.git/recipes/opie-dagger/
opie-dagger_1.2.4.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-opie-apps.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'clutter-gtk-0.6' (but
/home/frans/workspace/tst/openembedded.git/recipes/clutter/
clutter-gtk-0.6_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'udev-compat-wrapper' (but
/home/frans/workspace/tst/openembedded.git/recipes/udev/
udev-compat141_141.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'udev-compat141' (but
/home/frans/workspace/tst/openembedded.git/recipes/udev/
udev-compat141_141.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-openprotium' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_SSH_DAEMON}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_DEV_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_INIT_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_LOGIN_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-etk' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-settings_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-python-sharprom' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-minimal.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libmsgenabler2' (but
/home/frans/workspace/tst/openembedded.git/recipes/gpephone/
libmsgenabler2_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libmsip' (but
/home/frans/workspace/tst/openembedded.git/recipes/minisip/libmsip_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-openmoko-python-devel' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-python-devel.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'matchbox-panel-2-applets' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-base.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-xqtlauncher' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-xqtlauncher.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqtlauncher-blackbox-config' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-xqtlauncher.bb,
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher-blackbox-config.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'omoney' (but
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'opkg-ipkg-compat' (but
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'e2fsprogs-libs-dev' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-target.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libpng12-dev' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-target.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'nylon-feed' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/nylon-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-mamona-base' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xserver-kdrive-xomap' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'nodejs' (but
/home/frans/workspace/tst/openembedded.git/recipes/esc/esc-node-demo_git.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xvidcap' (but
/home/frans/workspace/tst/openembedded.git/recipes/xvidcap/
xvidcap_1.1.7rc1.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'virtual/xserver' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-gpe.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-base' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-apps' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-libs-install' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-theme' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-feed' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-uuid' (but
/home/frans/workspace/tst/openembedded.git/recipes/networkmanager/
cnetworkmanager_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'etk'
ERROR: Nothing RPROVIDES 'sugar-web-activity'
ERROR: Nothing RPROVIDES 'libgpepimc-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/libgpepimc/
libgpepimc-hildon_0.5.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-base-lib'
ERROR: Nothing RPROVIDES 'hildon-libs'
ERROR: Nothing RPROVIDES 'gconf-osso'
ERROR: Nothing RPROVIDES 'epsilon'
ERROR: Nothing RPROVIDES 'libmsip0'
ERROR: Nothing RPROVIDES 'libmikey0'
ERROR: Nothing RPROVIDES 'xmu'
ERROR: Nothing RPROVIDES 'evas-fb'
ERROR: Nothing RPROVIDES 'esmart-fb'
ERROR: Nothing RPROVIDES 'imlib2-fb'
ERROR: Nothing RPROVIDES 'efl++-fb'
ERROR: Nothing RPROVIDES 'codec-engine'
ERROR: Nothing RPROVIDES 'sword'
ERROR: Nothing RPROVIDES 'clutter-0.6'
ERROR: Nothing RPROVIDES 'libmnetutil0'
ERROR: Nothing RPROVIDES 'xdamage'
ERROR: Nothing RPROVIDES 'ti-codec-engine-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-codec-combo-omap3530-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-xdctools-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-dmai-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-dspbios-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-cgt6x-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-legacy-dvsdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'etk-native'
ERROR: Nothing RPROVIDES 'bluez-libs-3.36'
auncher' (but /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-xqtlauncher.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqtlauncher-blackbox-config' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-xqtlauncher.bb,
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher-blackbox-config.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'omoney' (but
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'opkg-ipkg-compat' (but
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'e2fsprogs-libs-dev' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-target.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libpng12-dev' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-target.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'nylon-feeERROR: Nothing RPROVIDES 'exhibit' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/e17/exhibit_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'om-locations' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-locations_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'om-settings' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'assassin' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin-thumbnail_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'assassin-thumbnail' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-feed.bb,
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
assassin-thumbnail_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-hmm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-itools' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-lightmediascanner' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-python-devel.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-pyreverse' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-snmplib' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-spyro' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-urwid' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-vmaps' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'twisted' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-python.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqt2' (but
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher.bb, /home/frans/workspace/tst/openembedded.git/recipes/xqt2/
xqt2_20060509.bb, /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-qpe.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqtlauncher' (but
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher.bb, /home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-xqtlauncher.bb,
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher-blackbox-config.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gstreamer-ti-demo-script' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-gstreamer-ti.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-demo-x11' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libgles-omap3-demos' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bc-cat-omap3-module-tests' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-demo-x11.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'edje-player' (but
/home/frans/workspace/tst/openembedded.git/recipes/e17/edje-player_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'edje-editor' (but
/home/frans/workspace/tst/openembedded.git/recipes/e17/edje-editor_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'sugar-fructose' (but
/home/frans/workspace/tst/openembedded.git/recipes/sugar/sugar-fructose.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '|' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-base.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'e2fsprogs-uuidgen' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-base.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-todo-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/gpe-todo/
gpe-todo-hildon_0.55.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'evolve' (but
/home/frans/workspace/tst/openembedded.git/recipes/efl1/evolve_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-application-installer' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
osso-application-installer_1.0.03-1.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bluez-utils-compat' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-gpephone.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'diversity-radar' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
diversity-radar_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'lessertunjo' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
lessertunjo_0.0.10.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'omview' (but
/home/frans/workspace/tst/openembedded.git/recipes/omview/omview_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'epsilon-thumbd' (but
/home/frans/workspace/tst/openembedded.git/recipes/omview/omview_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'bt950-cs' (but
/home/frans/workspace/tst/openembedded.git/recipes/bt950-cs/bt950-cs_0.1.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'minisip' (but
/home/frans/workspace/tst/openembedded.git/recipes/minisip/minisip_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'systemtap' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-systemtap.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-mamona-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-mamona-systemtap.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-applets' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-games' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-inputmethods' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-multimedia' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-emulators' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-applications' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-fonts' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-qpe-settings' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie-all.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'aterm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona-wm.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'dspgw-utils' (but
/home/frans/workspace/tst/openembedded.git/recipes/mamona/
mamona-sound-n800_0.1.0.bb,
/home/frans/workspace/tst/openembedded.git/recipes/mamona/
mamona-sound-n770_0.1.0.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ipkgorphan' (but
/home/frans/workspace/tst/openembedded.git/recipes/ipkg/ipkgorphan_0.0.1.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'openmoko-today' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-base/
openmoko-session_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'comic-reader' (but
/home/frans/workspace/tst/openembedded.git/recipes/comic-reader/
comic-reader_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-status-bar' (but
/home/frans/workspace/tst/openembedded.git/recipes/maemo/
hildon-status-bar_0.8.11-1.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'angstrom-bootmanager' (but
/home/frans/workspace/tst/openembedded.git/recipes/angstrom/
angstrom-bootmanager.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'fso-apm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-fso2-compliance.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'vlc-davinci' (but
/home/frans/workspace/tst/openembedded.git/recipes/vlc/vlc-davinci_0.8.6h.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal-cli' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal-apps' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'eflpp' (but
/home/frans/workspace/tst/openembedded.git/recipes/efl1/eflpp_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ipkg' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bb,
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-sdk-sbox-gpe' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-sdk-sbox-gpe.bb,
/home/frans/workspace/tst/openembedded.git/recipes/meta/
meta-toolchain-gpe-sbox.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-opie-bluetooth' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-opie-irda' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-opie.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'outo' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-initscripts' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-thumbnail' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-lgpl' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libhildonbase' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libhildonwidgets' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-fm' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-home' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-navigator' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'osso-screenshot-tool' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-contacts-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'gpe-mini-browser-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-maemo.bb,
/home/frans/workspace/tst/openembedded.git/recipes/gpe-mini-browser/
gpe-mini-browser-hildon_0.17.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'opie-dagger' (but
/home/frans/workspace/tst/openembedded.git/recipes/opie-dagger/
opie-dagger_1.2.4.bb,
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-opie-apps.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'clutter-gtk-0.6' (but
/home/frans/workspace/tst/openembedded.git/recipes/clutter/
clutter-gtk-0.6_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'udev-compat-wrapper' (but
/home/frans/workspace/tst/openembedded.git/recipes/udev/
udev-compat141_141.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'udev-compat141' (but
/home/frans/workspace/tst/openembedded.git/recipes/udev/
udev-compat141_141.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-openprotium' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_SSH_DAEMON}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_DEV_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_INIT_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES '${DISTRO_LOGIN_MANAGER}' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-openprotium.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-etk' (but
/home/frans/workspace/tst/openembedded.git/recipes/openmoko-projects/
om-settings_svn.bb,
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-python-sharprom' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-python-sharprom_20060425.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-minimal' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-minimal.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libmsgenabler2' (but
/home/frans/workspace/tst/openembedded.git/recipes/gpephone/
libmsgenabler2_svn.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libmsip' (but
/home/frans/workspace/tst/openembedded.git/recipes/minisip/libmsip_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-openmoko-python-devel' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-python-devel.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'matchbox-panel-2-applets' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-openmoko-base.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-xqtlauncher' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-xqtlauncher.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xqtlauncher-blackbox-config' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-xqtlauncher.bb,
/home/frans/workspace/tst/openembedded.git/recipes/xqtlauncher/
xqtlauncher-blackbox-config.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'omoney' (but
/home/frans/workspace/tst/openembedded.git/recipes/omoney/omoney_svn.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'opkg-ipkg-compat' (but
/home/frans/workspace/tst/openembedded.git/recipes/opkg/opkg-ipkg-compat.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'e2fsprogs-libs-dev' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-target.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'libpng12-dev' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-target.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'nylon-feed' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/nylon-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-mamona-base' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xserver-kdrive-xomap' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'nodejs' (but
/home/frans/workspace/tst/openembedded.git/recipes/esc/esc-node-demo_git.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xvidcap' (but
/home/frans/workspace/tst/openembedded.git/recipes/xvidcap/
xvidcap_1.1.7rc1.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'virtual/xserver' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-gpe.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-base' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-apps' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-libs-install' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-theme' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-feed' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-uuid' (but
/home/frans/workspace/tst/openembedded.git/recipes/networkmanager/
cnetworkmanager_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'etk'
ERROR: Nothing RPROVIDES 'sugar-web-activity'
ERROR: Nothing RPROVIDES 'libgpepimc-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/libgpepimc/
libgpepimc-hildon_0.5.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-base-lib'
ERROR: Nothing RPROVIDES 'hildon-libs'
ERROR: Nothing RPROVIDES 'gconf-osso'
ERROR: Nothing RPROVIDES 'epsilon'
ERROR: Nothing RPROVIDES 'libmsip0'
ERROR: Nothing RPROVIDES 'libmikey0'
ERROR: Nothing RPROVIDES 'xmu'
ERROR: Nothing RPROVIDES 'evas-fb'
ERROR: Nothing RPROVIDES 'esmart-fb'
ERROR: Nothing RPROVIDES 'imlib2-fb'
ERROR: Nothing RPROVIDES 'efl++-fb'
ERROR: Nothing RPROVIDES 'codec-engine'
ERROR: Nothing RPROVIDES 'sword'
ERROR: Nothing RPROVIDES 'clutter-0.6'
ERROR: Nothing RPROVIDES 'libmnetutil0'
ERROR: Nothing RPROVIDES 'xdamage'
ERROR: Nothing RPROVIDES 'ti-codec-engine-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-codec-combo-omap3530-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-xdctools-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-dmai-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-dspbios-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-cgt6x-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-legacy-dvsdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'etk-native'
ERROR: Nothing RPROVIDES 'bluez-libs-3.36'
d' (but /home/frans/workspace/tst/openembedded.git/recipes/meta/
nylon-feed.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-mamona-base' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xserver-kdrive-xomap' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-mamona.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'nodejs' (but
/home/frans/workspace/tst/openembedded.git/recipes/esc/esc-node-demo_git.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'xvidcap' (but
/home/frans/workspace/tst/openembedded.git/recipes/xvidcap/
xvidcap_1.1.7rc1.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'virtual/xserver' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-gpe.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-base' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-apps' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-libs-install' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'maemo-task-theme' (but
/home/frans/workspace/tst/openembedded.git/recipes/meta/meta-maemo.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'task-shr-feed' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/task-shr-feed.bbRDEPENDS
on or otherwise requires it)
ERROR: Nothing RPROVIDES 'python-uuid' (but
/home/frans/workspace/tst/openembedded.git/recipes/networkmanager/
cnetworkmanager_git.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'etk'
ERROR: Nothing RPROVIDES 'sugar-web-activity'
ERROR: Nothing RPROVIDES 'libgpepimc-hildon' (but
/home/frans/workspace/tst/openembedded.git/recipes/libgpepimc/
libgpepimc-hildon_0.5.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'hildon-base-lib'
ERROR: Nothing RPROVIDES 'hildon-libs'
ERROR: Nothing RPROVIDES 'gconf-osso'
ERROR: Nothing RPROVIDES 'epsilon'
ERROR: Nothing RPROVIDES 'libmsip0'
ERROR: Nothing RPROVIDES 'libmikey0'
ERROR: Nothing RPROVIDES 'xmu'
ERROR: Nothing RPROVIDES 'evas-fb'
ERROR: Nothing RPROVIDES 'esmart-fb'
ERROR: Nothing RPROVIDES 'imlib2-fb'
ERROR: Nothing RPROVIDES 'efl++-fb'
ERROR: Nothing RPROVIDES 'codec-engine'
ERROR: Nothing RPROVIDES 'sword'
ERROR: Nothing RPROVIDES 'clutter-0.6'
ERROR: Nothing RPROVIDES 'libmnetutil0'
ERROR: Nothing RPROVIDES 'xdamage'
ERROR: Nothing RPROVIDES 'ti-codec-engine-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-codec-combo-omap3530-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-xdctools-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-dmai-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-dspbios-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-cgt6x-sdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'ti-legacy-dvsdk' (but
/home/frans/workspace/tst/openembedded.git/recipes/tasks/
task-arago-toolchain-dvsdk-host.bb RDEPENDS on or otherwise requires it)
ERROR: Nothing RPROVIDES 'etk-native'
ERROR: Nothing RPROVIDES 'bluez-libs-3.36'

Same questions as before:
fix/ignore/move to non-buildable dir/remove


preferred versions errors:
==================

apparently there is some pinning of recipes on versions that do not exist
any more.
Guess this is a distro issue.
List:
NOTE: preferred version 1_0_3 of ti-dm365mm-module not available (for item
ti-dm365mm-module)
NOTE: preferred version 1.2.4 of opie-securityplugin-dummy not available
(for item opie-securityplugin-dummy)
NOTE: preferred version 1_13 of ti-dm355mm-module not available (for item
ti-dm355mm-module)
NOTE: preferred version 3_10_00_02 of ti-codecs-dm365 not available (for
item ti-codecs-dm365)
NOTE: preferred version 1_0_3 of ti-dm365mm-module not available (for item
ti-dm365mm-module)
NOTE: preferred version 1.2.4 of opie-securityplugin-dummy not available
(for item opie-securityplugin-dummy)
NOTE: preferred version 1_13 of ti-dm355mm-module not available (for item
ti-dm355mm-module)
NOTE: preferred version 151 of udev not available (for item
libvolume-id-dev)
NOTE: preferred version 3_10_00_02 of ti-codecs-dm365 not available (for
item ti-codecs-dm365)

Seems ti and udev recipes are involved


unbuildable targets errors:
===================

Quite a list (of course triggered by the above:
[message continues after the list]

NOTE: Runtime target 'exhibit' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['exhibit']
NOTE: Runtime target 'task-openmoko-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko-feed',
'exhibit']
NOTE: Runtime target 'om-locations' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['om-locations']
NOTE: Runtime target 'om-settings' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['om-settings']
NOTE: Runtime target 'assassin' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['assassin']
NOTE: Runtime target 'assassin-thumbnail' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['assassin-thumbnail']
NOTE: Runtime target 'python-hmm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-hmm']
NOTE: Runtime target 'python-itools' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-itools']
NOTE: Runtime target 'python-lightmediascanner' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-lightmediascanner']
NOTE: Runtime target 'python-pyreverse' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-pyreverse']
NOTE: Runtime target 'python-snmplib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-snmplib']
NOTE: Runtime target 'python-spyro' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-spyro']
NOTE: Runtime target 'python-urwid' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-urwid']
NOTE: Runtime target 'python-vmaps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-vmaps']
NOTE: Runtime target 'twisted' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['twisted']
NOTE: Runtime target 'xqt2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xqt2']
NOTE: Runtime target 'xqtlauncher' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xqtlauncher']
NOTE: Runtime target 'gstreamer-ti-demo-script' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gstreamer-ti-demo-script']
NOTE: Runtime target 'task-gstreamer-ti' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-gstreamer-ti',
'gstreamer-ti-demo-script']
NOTE: Runtime target 'task-demo-x11' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-demo-x11']
NOTE: Runtime target 'libgles-omap3-demos' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgles-omap3-demos']
NOTE: Runtime target 'bc-cat-omap3-module-tests' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bc-cat-omap3-module-tests']
NOTE: Runtime target 'edje-player' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['edje-player']
NOTE: Runtime target 'edje-editor' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['edje-editor']
NOTE: Runtime target 'sugar-fructose' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sugar-fructose']
NOTE: Runtime target '|' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['|']
NOTE: Runtime target 'e2fsprogs-uuidgen' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['e2fsprogs-uuidgen']
NOTE: Runtime target 'gpe-todo-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-todo-hildon']
NOTE: Runtime target 'evolve' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['evolve']
NOTE: Runtime target 'osso-application-installer' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['osso-application-installer']
NOTE: Runtime target 'bluez-utils-compat' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-compat']
NOTE: Runtime target 'task-mamona' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona',
'bluez-utils-compat']
NOTE: Runtime target 'diversity-radar' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['diversity-radar']
NOTE: Runtime target 'lessertunjo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['lessertunjo']
NOTE: Runtime target 'omview' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omview']
NOTE: Runtime target 'epsilon-thumbd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['epsilon-thumbd']
NOTE: Runtime target 'bt950-cs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bt950-cs']
NOTE: Runtime target 'minisip' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['minisip']
NOTE: Runtime target 'systemtap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['systemtap']
NOTE: Runtime target 'task-mamona-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona-sdk']
NOTE: Runtime target 'task-qpe-applets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-applets']
NOTE: Runtime target 'task-qpe-games' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-games']
NOTE: Runtime target 'task-qpe-inputmethods' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-inputmethods']
NOTE: Runtime target 'task-qpe-multimedia' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-multimedia']
NOTE: Runtime target 'task-qpe-emulators' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-emulators']
NOTE: Runtime target 'task-qpe-applications' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-applications']
NOTE: Runtime target 'task-qpe-fonts' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-fonts']
NOTE: Runtime target 'task-qpe-settings' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-settings']
NOTE: Runtime target 'aterm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['aterm']
NOTE: Runtime target 'dspgw-utils' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dspgw-utils']
NOTE: Runtime target 'ipkgorphan' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ipkgorphan']
NOTE: Runtime target 'openmoko-today' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openmoko-today']
NOTE: Runtime target 'openmoko-session' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openmoko-session',
'openmoko-today']
NOTE: Runtime target 'comic-reader' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['comic-reader']
NOTE: Runtime target 'hildon-status-bar' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-status-bar']
NOTE: Runtime target 'angstrom-bootmanager' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['angstrom-bootmanager']
NOTE: Runtime target 'fso-apm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['fso-apm']
NOTE: Runtime target 'task-fso2-compliance' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-fso2-compliance',
'fso-apm']
NOTE: Runtime target 'vlc-davinci' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['vlc-davinci']
NOTE: Runtime target 'task-shr-minimal-cli' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal-cli']
NOTE: Runtime target 'task-shr-minimal-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal-apps']
NOTE: Runtime target 'eflpp' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['eflpp']
NOTE: Runtime target 'ipkg' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ipkg']
NOTE: Runtime target 'task-sdk-sbox-gpe' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-sdk-sbox-gpe']
NOTE: Runtime target 'task-opie-bluetooth' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-bluetooth']
NOTE: Runtime target 'task-opie-irda' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-irda']
NOTE: Runtime target 'outo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['outo']
NOTE: Runtime target 'hildon-initscripts' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-initscripts']
NOTE: Runtime target 'osso-thumbnail' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['osso-thumbnail']
NOTE: Runtime target 'hildon-lgpl' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-lgpl']
NOTE: Runtime target 'libhildonbase' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libhildonbase']
NOTE: Runtime target 'libhildonwidgets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libhildonwidgets']
NOTE: Runtime target 'hildon-fm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-fm']
NOTE: Runtime target 'hildon-home' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-home']
NOTE: Runtime target 'hildon-navigator' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-navigator']
NOTE: Runtime target 'osso-screenshot-tool' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['osso-screenshot-tool']
NOTE: Runtime target 'gpe-contacts-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-contacts-hildon']
NOTE: Runtime target 'gpe-mini-browser-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-mini-browser-hildon']
NOTE: Runtime target 'opie-dagger' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['opie-dagger']
NOTE: Runtime target 'task-opie-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-apps',
'opie-dagger']
NOTE: Runtime target 'task-opie-extra-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-extra-apps',
'opie-dagger']
NOTE: Runtime target 'clutter-gtk-0.6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['clutter-gtk-0.6']
NOTE: Runtime target 'udev-compat-wrapper' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['udev-compat-wrapper']
NOTE: Runtime target 'udev-compat141' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['udev-compat141']
NOTE: Runtime target 'task-openprotium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openprotium']
NOTE: Runtime target '${DISTRO_SSH_DAEMON}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_SSH_DAEMON}']
NOTE: Runtime target '${DISTRO_DEV_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_DEV_MANAGER}']
NOTE: Runtime target '${DISTRO_INIT_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_INIT_MANAGER}']
NOTE: Runtime target '${DISTRO_LOGIN_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_LOGIN_MANAGER}']
NOTE: Runtime target 'python-etk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-etk']
NOTE: Runtime target 'task-python-sharprom' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-python-sharprom']
NOTE: Runtime target 'task-shr-minimal' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal']
NOTE: Runtime target 'libmsgenabler2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsgenabler2']
NOTE: Runtime target 'libmsip' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsip']
NOTE: Runtime target 'task-openmoko-python-devel' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['task-openmoko-python-devel']
NOTE: Runtime target 'matchbox-panel-2-applets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['matchbox-panel-2-applets']
NOTE: Runtime target 'task-openmoko-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko-base',
'matchbox-panel-2-applets']
NOTE: Runtime target 'task-openmoko' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko',
'task-openmoko-base', 'matchbox-panel-2-applets']
NOTE: Runtime target 'task-xqtlauncher' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-xqtlauncher']
NOTE: Runtime target 'xqtlauncher-blackbox-config' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['xqtlauncher-blackbox-config']
NOTE: Runtime target 'omoney' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omoney']
NOTE: Runtime target 'opkg-ipkg-compat' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['opkg-ipkg-compat']
NOTE: Runtime target 'e2fsprogs-libs-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['e2fsprogs-libs-dev']
NOTE: Runtime target 'task-arago-toolchain-target' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['task-arago-toolchain-target',
'e2fsprogs-libs-dev']
NOTE: Runtime target 'task-arago-toolchain-dvsdk-target' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['task-arago-toolchain-dvsdk-target', 'task-arago-toolchain-target',
'e2fsprogs-libs-dev']
NOTE: Runtime target 'libpng12-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libpng12-dev']
NOTE: Runtime target 'nylon-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nylon-feed']
NOTE: Runtime target 'task-mamona-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona-base']
NOTE: Runtime target 'xserver-kdrive-xomap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xserver-kdrive-xomap']
NOTE: Runtime target 'nodejs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nodejs']
NOTE: Runtime target 'esc-node-demo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['esc-node-demo', 'nodejs']
NOTE: Runtime target 'xvidcap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xvidcap']
NOTE: Runtime target 'virtual/xserver' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['virtual/xserver']
NOTE: Runtime target 'maemo-task-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-base']
NOTE: Runtime target 'maemo-task-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-apps']
NOTE: Runtime target 'maemo-task-libs-install' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-libs-install']
NOTE: Runtime target 'maemo-task-theme' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-theme']
NOTE: Runtime target 'task-shr-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-feed']
NOTE: Runtime target 'python-uuid' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-uuid']
NOTE: Runtime target 'cnetworkmanager' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['cnetworkmanager',
'python-uuid']
NOTE: Runtime target 'etk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['etk']
NOTE: Runtime target 'sugar-web-activity' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sugar-web-activity']
NOTE: Runtime target 'libgpepimc-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgpepimc-hildon']
NOTE: Runtime target 'hildon-base-lib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-base-lib']
NOTE: Runtime target 'hildon-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-libs']
NOTE: Runtime target 'gconf-osso' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gconf-osso']
NOTE: Runtime target 'epsilon' is unbuildable, removing...
Missing or unbuildable dependeNOTE: Runtime target 'exhibit' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['exhibit']
NOTE: Runtime target 'task-openmoko-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko-feed',
'exhibit']
NOTE: Runtime target 'om-locations' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['om-locations']
NOTE: Runtime target 'om-settings' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['om-settings']
NOTE: Runtime target 'assassin' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['assassin']
NOTE: Runtime target 'assassin-thumbnail' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['assassin-thumbnail']
NOTE: Runtime target 'python-hmm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-hmm']
NOTE: Runtime target 'python-itools' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-itools']
NOTE: Runtime target 'python-lightmediascanner' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-lightmediascanner']
NOTE: Runtime target 'python-pyreverse' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-pyreverse']
NOTE: Runtime target 'python-snmplib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-snmplib']
NOTE: Runtime target 'python-spyro' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-spyro']
NOTE: Runtime target 'python-urwid' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-urwid']
NOTE: Runtime target 'python-vmaps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-vmaps']
NOTE: Runtime target 'twisted' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['twisted']
NOTE: Runtime target 'xqt2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xqt2']
NOTE: Runtime target 'xqtlauncher' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xqtlauncher']
NOTE: Runtime target 'gstreamer-ti-demo-script' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gstreamer-ti-demo-script']
NOTE: Runtime target 'task-gstreamer-ti' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-gstreamer-ti',
'gstreamer-ti-demo-script']
NOTE: Runtime target 'task-demo-x11' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-demo-x11']
NOTE: Runtime target 'libgles-omap3-demos' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgles-omap3-demos']
NOTE: Runtime target 'bc-cat-omap3-module-tests' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bc-cat-omap3-module-tests']
NOTE: Runtime target 'edje-player' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['edje-player']
NOTE: Runtime target 'edje-editor' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['edje-editor']
NOTE: Runtime target 'sugar-fructose' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sugar-fructose']
NOTE: Runtime target '|' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['|']
NOTE: Runtime target 'e2fsprogs-uuidgen' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['e2fsprogs-uuidgen']
NOTE: Runtime target 'gpe-todo-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-todo-hildon']
NOTE: Runtime target 'evolve' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['evolve']
NOTE: Runtime target 'osso-application-installer' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['osso-application-installer']
NOTE: Runtime target 'bluez-utils-compat' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-compat']
NOTE: Runtime target 'task-mamona' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona',
'bluez-utils-compat']
NOTE: Runtime target 'diversity-radar' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['diversity-radar']
NOTE: Runtime target 'lessertunjo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['lessertunjo']
NOTE: Runtime target 'omview' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omview']
NOTE: Runtime target 'epsilon-thumbd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['epsilon-thumbd']
NOTE: Runtime target 'bt950-cs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bt950-cs']
NOTE: Runtime target 'minisip' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['minisip']
NOTE: Runtime target 'systemtap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['systemtap']
NOTE: Runtime target 'task-mamona-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona-sdk']
NOTE: Runtime target 'task-qpe-applets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-applets']
NOTE: Runtime target 'task-qpe-games' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-games']
NOTE: Runtime target 'task-qpe-inputmethods' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-inputmethods']
NOTE: Runtime target 'task-qpe-multimedia' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-multimedia']
NOTE: Runtime target 'task-qpe-emulators' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-emulators']
NOTE: Runtime target 'task-qpe-applications' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-applications']
NOTE: Runtime target 'task-qpe-fonts' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-fonts']
NOTE: Runtime target 'task-qpe-settings' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-settings']
NOTE: Runtime target 'aterm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['aterm']
NOTE: Runtime target 'dspgw-utils' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dspgw-utils']
NOTE: Runtime target 'ipkgorphan' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ipkgorphan']
NOTE: Runtime target 'openmoko-today' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openmoko-today']
NOTE: Runtime target 'openmoko-session' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openmoko-session',
'openmoko-today']
NOTE: Runtime target 'comic-reader' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['comic-reader']
NOTE: Runtime target 'hildon-status-bar' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-status-bar']
NOTE: Runtime target 'angstrom-bootmanager' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['angstrom-bootmanager']
NOTE: Runtime target 'fso-apm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['fso-apm']
NOTE: Runtime target 'task-fso2-compliance' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-fso2-compliance',
'fso-apm']
NOTE: Runtime target 'vlc-davinci' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['vlc-davinci']
NOTE: Runtime target 'task-shr-minimal-cli' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal-cli']
NOTE: Runtime target 'task-shr-minimal-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal-apps']
NOTE: Runtime target 'eflpp' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['eflpp']
NOTE: Runtime target 'ipkg' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ipkg']
NOTE: Runtime target 'task-sdk-sbox-gpe' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-sdk-sbox-gpe']
NOTE: Runtime target 'task-opie-bluetooth' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-bluetooth']
NOTE: Runtime target 'task-opie-irda' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-irda']
NOTE: Runtime target 'outo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['outo']
NOTE: Runtime target 'hildon-initscripts' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-initscripts']
NOTE: Runtime target 'osso-thumbnail' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['osso-thumbnail']
NOTE: Runtime target 'hildon-lgpl' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-lgpl']
NOTE: Runtime target 'libhildonbase' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libhildonbase']
NOTE: Runtime target 'libhildonwidgets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libhildonwidgets']
NOTE: Runtime target 'hildon-fm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-fm']
NOTE: Runtime target 'hildon-home' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-home']
NOTE: Runtime target 'hildon-navigator' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-navigator']
NOTE: Runtime target 'osso-screenshot-tool' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['osso-screenshot-tool']
NOTE: Runtime target 'gpe-contacts-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-contacts-hildon']
NOTE: Runtime target 'gpe-mini-browser-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-mini-browser-hildon']
NOTE: Runtime target 'opie-dagger' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['opie-dagger']
NOTE: Runtime target 'task-opie-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-apps',
'opie-dagger']
NOTE: Runtime target 'task-opie-extra-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-extra-apps',
'opie-dagger']
NOTE: Runtime target 'clutter-gtk-0.6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['clutter-gtk-0.6']
NOTE: Runtime target 'udev-compat-wrapper' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['udev-compat-wrapper']
NOTE: Runtime target 'udev-compat141' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['udev-compat141']
NOTE: Runtime target 'task-openprotium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openprotium']
NOTE: Runtime target '${DISTRO_SSH_DAEMON}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_SSH_DAEMON}']
NOTE: Runtime target '${DISTRO_DEV_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_DEV_MANAGER}']
NOTE: Runtime target '${DISTRO_INIT_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_INIT_MANAGER}']
NOTE: Runtime target '${DISTRO_LOGIN_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_LOGIN_MANAGER}']
NOTE: Runtime target 'python-etk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-etk']
NOTE: Runtime target 'task-python-sharprom' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-python-sharprom']
NOTE: Runtime target 'task-shr-minimal' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal']
NOTE: Runtime target 'libmsgenabler2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsgenabler2']
NOTE: Runtime target 'libmsip' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsip']
NOTE: Runtime target 'task-openmoko-python-devel' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['task-openmoko-python-devel']
NOTE: Runtime target 'matchbox-panel-2-applets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['matchbox-panel-2-applets']
NOTE: Runtime target 'task-openmoko-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko-base',
'matchbox-panel-2-applets']
NOTE: Runtime target 'task-openmoko' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko',
'task-openmoko-base', 'matchbox-panel-2-applets']
NOTE: Runtime target 'task-xqtlauncher' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-xqtlauncher']
NOTE: Runtime target 'xqtlauncher-blackbox-config' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['xqtlauncher-blackbox-config']
NOTE: Runtime target 'omoney' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omoney']
NOTE: Runtime target 'opkg-ipkg-compat' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['opkg-ipkg-compat']
NOTE: Runtime target 'e2fsprogs-libs-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['e2fsprogs-libs-dev']
NOTE: Runtime target 'task-arago-toolchain-target' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['task-arago-toolchain-target',
'e2fsprogs-libs-dev']
NOTE: Runtime target 'task-arago-toolchain-dvsdk-target' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['task-arago-toolchain-dvsdk-target', 'task-arago-toolchain-target',
'e2fsprogs-libs-dev']
NOTE: Runtime target 'libpng12-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libpng12-dev']
NOTE: Runtime target 'nylon-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nylon-feed']
NOTE: Runtime target 'task-mamona-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona-base']
NOTE: Runtime target 'xserver-kdrive-xomap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xserver-kdrive-xomap']
NOTE: Runtime target 'nodejs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nodejs']
NOTE: Runtime target 'esc-node-demo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['esc-node-demo', 'nodejs']
NOTE: Runtime target 'xvidcap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xvidcap']
NOTE: Runtime target 'virtual/xserver' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['virtual/xserver']
NOTE: Runtime target 'maemo-task-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-base']
NOTE: Runtime target 'maemo-task-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-apps']
NOTE: Runtime target 'maemo-task-libs-install' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-libs-install']
NOTE: Runtime target 'maemo-task-theme' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-theme']
NOTE: Runtime target 'task-shr-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-feed']
NOTE: Runtime target 'python-uuid' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-uuid']
NOTE: Runtime target 'cnetworkmanager' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['cnetworkmanager',
'python-uuid']
NOTE: Runtime target 'etk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['etk']
NOTE: Runtime target 'sugar-web-activity' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sugar-web-activity']
NOTE: Runtime target 'libgpepimc-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgpepimc-hildon']
NOTE: Runtime target 'hildon-base-lib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-base-lib']
NOTE: Runtime target 'hildon-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-libs']
NOTE: Runtime target 'gconf-osso' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gconf-osso']
NOTE: Runtime target 'epsilon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['epsilon']
NOTE: Runtime target 'libmsip0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsip0']
NOTE: Runtime target 'libmikey0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmikey0']
NOTE: Runtime target 'xmu' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xmu']
NOTE: Runtime target 'evas-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['evas-fb']
NOTE: Runtime target 'esmart-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['esmart-fb']
NOTE: Runtime target 'imlib2-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['imlib2-fb']
NOTE: Runtime target 'efl++-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['efl++-fb']
NOTE: Runtime target 'codec-engine' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['codec-engine']
NOTE: Runtime target 'sword' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sword']
NOTE: Runtime target 'clutter-0.6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['clutter-0.6']
NOTE: Runtime target 'libmnetutil0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmnetutil0']
NOTE: Runtime target 'xdamage' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xdamage']
NOTE: Runtime target 'bluez-cups-backend' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-cups-backend',
'bluez-libs-3.36']
NOTE: Runtime target 'bluez-gstreamer-plugin' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-gstreamer-plugin',
'bluez-libs-3.36']
NOTE: Runtime target 'bluez-utils-alsa' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-alsa',
'bluez-libs-3.36']
NOTE: Runtime target 'ti-codec-engine-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-codec-engine-sdk']
NOTE: Runtime target 'task-arago-toolchain-dvsdk-host' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['task-arago-toolchain-dvsdk-host', 'ti-codec-engine-sdk']
NOTE: Runtime target 'ti-codec-combo-omap3530-sdk' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['ti-codec-combo-omap3530-sdk']
NOTE: Runtime target 'ti-xdctools-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-xdctools-sdk']
NOTE: Runtime target 'ti-dmai-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-dmai-sdk']
NOTE: Runtime target 'ti-dspbios-sdk' is unbuildable, removing...
Missing or unbuildable dependeNOTE: Runtime target 'exhibit' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['exhibit']
NOTE: Runtime target 'task-openmoko-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko-feed',
'exhibit']
NOTE: Runtime target 'om-locations' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['om-locations']
NOTE: Runtime target 'om-settings' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['om-settings']
NOTE: Runtime target 'assassin' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['assassin']
NOTE: Runtime target 'assassin-thumbnail' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['assassin-thumbnail']
NOTE: Runtime target 'python-hmm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-hmm']
NOTE: Runtime target 'python-itools' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-itools']
NOTE: Runtime target 'python-lightmediascanner' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-lightmediascanner']
NOTE: Runtime target 'python-pyreverse' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-pyreverse']
NOTE: Runtime target 'python-snmplib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-snmplib']
NOTE: Runtime target 'python-spyro' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-spyro']
NOTE: Runtime target 'python-urwid' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-urwid']
NOTE: Runtime target 'python-vmaps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-vmaps']
NOTE: Runtime target 'twisted' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['twisted']
NOTE: Runtime target 'xqt2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xqt2']
NOTE: Runtime target 'xqtlauncher' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xqtlauncher']
NOTE: Runtime target 'gstreamer-ti-demo-script' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gstreamer-ti-demo-script']
NOTE: Runtime target 'task-gstreamer-ti' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-gstreamer-ti',
'gstreamer-ti-demo-script']
NOTE: Runtime target 'task-demo-x11' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-demo-x11']
NOTE: Runtime target 'libgles-omap3-demos' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgles-omap3-demos']
NOTE: Runtime target 'bc-cat-omap3-module-tests' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bc-cat-omap3-module-tests']
NOTE: Runtime target 'edje-player' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['edje-player']
NOTE: Runtime target 'edje-editor' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['edje-editor']
NOTE: Runtime target 'sugar-fructose' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sugar-fructose']
NOTE: Runtime target '|' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['|']
NOTE: Runtime target 'e2fsprogs-uuidgen' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['e2fsprogs-uuidgen']
NOTE: Runtime target 'gpe-todo-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-todo-hildon']
NOTE: Runtime target 'evolve' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['evolve']
NOTE: Runtime target 'osso-application-installer' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['osso-application-installer']
NOTE: Runtime target 'bluez-utils-compat' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-compat']
NOTE: Runtime target 'task-mamona' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona',
'bluez-utils-compat']
NOTE: Runtime target 'diversity-radar' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['diversity-radar']
NOTE: Runtime target 'lessertunjo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['lessertunjo']
NOTE: Runtime target 'omview' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omview']
NOTE: Runtime target 'epsilon-thumbd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['epsilon-thumbd']
NOTE: Runtime target 'bt950-cs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bt950-cs']
NOTE: Runtime target 'minisip' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['minisip']
NOTE: Runtime target 'systemtap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['systemtap']
NOTE: Runtime target 'task-mamona-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona-sdk']
NOTE: Runtime target 'task-qpe-applets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-applets']
NOTE: Runtime target 'task-qpe-games' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-games']
NOTE: Runtime target 'task-qpe-inputmethods' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-inputmethods']
NOTE: Runtime target 'task-qpe-multimedia' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-multimedia']
NOTE: Runtime target 'task-qpe-emulators' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-emulators']
NOTE: Runtime target 'task-qpe-applications' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-applications']
NOTE: Runtime target 'task-qpe-fonts' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-fonts']
NOTE: Runtime target 'task-qpe-settings' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-qpe-settings']
NOTE: Runtime target 'aterm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['aterm']
NOTE: Runtime target 'dspgw-utils' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dspgw-utils']
NOTE: Runtime target 'ipkgorphan' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ipkgorphan']
NOTE: Runtime target 'openmoko-today' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openmoko-today']
NOTE: Runtime target 'openmoko-session' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openmoko-session',
'openmoko-today']
NOTE: Runtime target 'comic-reader' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['comic-reader']
NOTE: Runtime target 'hildon-status-bar' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-status-bar']
NOTE: Runtime target 'angstrom-bootmanager' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['angstrom-bootmanager']
NOTE: Runtime target 'fso-apm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['fso-apm']
NOTE: Runtime target 'task-fso2-compliance' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-fso2-compliance',
'fso-apm']
NOTE: Runtime target 'vlc-davinci' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['vlc-davinci']
NOTE: Runtime target 'task-shr-minimal-cli' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal-cli']
NOTE: Runtime target 'task-shr-minimal-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal-apps']
NOTE: Runtime target 'eflpp' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['eflpp']
NOTE: Runtime target 'ipkg' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ipkg']
NOTE: Runtime target 'task-sdk-sbox-gpe' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-sdk-sbox-gpe']
NOTE: Runtime target 'task-opie-bluetooth' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-bluetooth']
NOTE: Runtime target 'task-opie-irda' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-irda']
NOTE: Runtime target 'outo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['outo']
NOTE: Runtime target 'hildon-initscripts' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-initscripts']
NOTE: Runtime target 'osso-thumbnail' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['osso-thumbnail']
NOTE: Runtime target 'hildon-lgpl' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-lgpl']
NOTE: Runtime target 'libhildonbase' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libhildonbase']
NOTE: Runtime target 'libhildonwidgets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libhildonwidgets']
NOTE: Runtime target 'hildon-fm' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-fm']
NOTE: Runtime target 'hildon-home' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-home']
NOTE: Runtime target 'hildon-navigator' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-navigator']
NOTE: Runtime target 'osso-screenshot-tool' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['osso-screenshot-tool']
NOTE: Runtime target 'gpe-contacts-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-contacts-hildon']
NOTE: Runtime target 'gpe-mini-browser-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gpe-mini-browser-hildon']
NOTE: Runtime target 'opie-dagger' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['opie-dagger']
NOTE: Runtime target 'task-opie-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-apps',
'opie-dagger']
NOTE: Runtime target 'task-opie-extra-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-opie-extra-apps',
'opie-dagger']
NOTE: Runtime target 'clutter-gtk-0.6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['clutter-gtk-0.6']
NOTE: Runtime target 'udev-compat-wrapper' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['udev-compat-wrapper']
NOTE: Runtime target 'udev-compat141' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['udev-compat141']
NOTE: Runtime target 'task-openprotium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openprotium']
NOTE: Runtime target '${DISTRO_SSH_DAEMON}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_SSH_DAEMON}']
NOTE: Runtime target '${DISTRO_DEV_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_DEV_MANAGER}']
NOTE: Runtime target '${DISTRO_INIT_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_INIT_MANAGER}']
NOTE: Runtime target '${DISTRO_LOGIN_MANAGER}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${DISTRO_LOGIN_MANAGER}']
NOTE: Runtime target 'python-etk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-etk']
NOTE: Runtime target 'task-python-sharprom' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-python-sharprom']
NOTE: Runtime target 'task-shr-minimal' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-minimal']
NOTE: Runtime target 'libmsgenabler2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsgenabler2']
NOTE: Runtime target 'libmsip' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsip']
NOTE: Runtime target 'task-openmoko-python-devel' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['task-openmoko-python-devel']
NOTE: Runtime target 'matchbox-panel-2-applets' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['matchbox-panel-2-applets']
NOTE: Runtime target 'task-openmoko-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko-base',
'matchbox-panel-2-applets']
NOTE: Runtime target 'task-openmoko' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-openmoko',
'task-openmoko-base', 'matchbox-panel-2-applets']
NOTE: Runtime target 'task-xqtlauncher' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-xqtlauncher']
NOTE: Runtime target 'xqtlauncher-blackbox-config' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['xqtlauncher-blackbox-config']
NOTE: Runtime target 'omoney' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omoney']
NOTE: Runtime target 'opkg-ipkg-compat' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['opkg-ipkg-compat']
NOTE: Runtime target 'e2fsprogs-libs-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['e2fsprogs-libs-dev']
NOTE: Runtime target 'task-arago-toolchain-target' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['task-arago-toolchain-target',
'e2fsprogs-libs-dev']
NOTE: Runtime target 'task-arago-toolchain-dvsdk-target' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['task-arago-toolchain-dvsdk-target', 'task-arago-toolchain-target',
'e2fsprogs-libs-dev']
NOTE: Runtime target 'libpng12-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libpng12-dev']
NOTE: Runtime target 'nylon-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nylon-feed']
NOTE: Runtime target 'task-mamona-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-mamona-base']
NOTE: Runtime target 'xserver-kdrive-xomap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xserver-kdrive-xomap']
NOTE: Runtime target 'nodejs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nodejs']
NOTE: Runtime target 'esc-node-demo' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['esc-node-demo', 'nodejs']
NOTE: Runtime target 'xvidcap' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xvidcap']
NOTE: Runtime target 'virtual/xserver' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['virtual/xserver']
NOTE: Runtime target 'maemo-task-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-base']
NOTE: Runtime target 'maemo-task-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-apps']
NOTE: Runtime target 'maemo-task-libs-install' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-libs-install']
NOTE: Runtime target 'maemo-task-theme' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['maemo-task-theme']
NOTE: Runtime target 'task-shr-feed' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['task-shr-feed']
NOTE: Runtime target 'python-uuid' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python-uuid']
NOTE: Runtime target 'cnetworkmanager' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['cnetworkmanager',
'python-uuid']
NOTE: Runtime target 'etk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['etk']
NOTE: Runtime target 'sugar-web-activity' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sugar-web-activity']
NOTE: Runtime target 'libgpepimc-hildon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgpepimc-hildon']
NOTE: Runtime target 'hildon-base-lib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-base-lib']
NOTE: Runtime target 'hildon-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hildon-libs']
NOTE: Runtime target 'gconf-osso' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['gconf-osso']
NOTE: Runtime target 'epsilon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['epsilon']
NOTE: Runtime target 'libmsip0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsip0']
NOTE: Runtime target 'libmikey0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmikey0']
NOTE: Runtime target 'xmu' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xmu']
NOTE: Runtime target 'evas-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['evas-fb']
NOTE: Runtime target 'esmart-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['esmart-fb']
NOTE: Runtime target 'imlib2-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['imlib2-fb']
NOTE: Runtime target 'efl++-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['efl++-fb']
NOTE: Runtime target 'codec-engine' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['codec-engine']
NOTE: Runtime target 'sword' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sword']
NOTE: Runtime target 'clutter-0.6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['clutter-0.6']
NOTE: Runtime target 'libmnetutil0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmnetutil0']
NOTE: Runtime target 'xdamage' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xdamage']
NOTE: Runtime target 'bluez-cups-backend' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-cups-backend',
'bluez-libs-3.36']
NOTE: Runtime target 'bluez-gstreamer-plugin' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-gstreamer-plugin',
'bluez-libs-3.36']
NOTE: Runtime target 'bluez-utils-alsa' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-alsa',
'bluez-libs-3.36']
NOTE: Runtime target 'ti-codec-engine-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-codec-engine-sdk']
NOTE: Runtime target 'task-arago-toolchain-dvsdk-host' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['task-arago-toolchain-dvsdk-host', 'ti-codec-engine-sdk']
NOTE: Runtime target 'ti-codec-combo-omap3530-sdk' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['ti-codec-combo-omap3530-sdk']
NOTE: Runtime target 'ti-xdctools-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-xdctools-sdk']
NOTE: Runtime target 'ti-dmai-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-dmai-sdk']
NOTE: Runtime target 'ti-dspbios-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-dspbios-sdk']
NOTE: Runtime target 'ti-cgt6x-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-cgt6x-sdk']
NOTE: Runtime target 'ti-legacy-dvsdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-legacy-dvsdk']
NOTE: Runtime target 'etk-native' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['etk-native']
NOTE: Runtime target 'bluez-libs-3.36' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-libs-3.36']
ncy chain was: ['ti-dspbios-sdk']
NOTE: Runtime target 'ti-cgt6x-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-cgt6x-sdk']
NOTE: Runtime target 'ti-legacy-dvsdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-legacy-dvsdk']
NOTE: Runtime target 'etk-native' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['etk-native']
NOTE: Runtime target 'bluez-libs-3.36' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-libs-3.36']
ncy chain was: ['epsilon']
NOTE: Runtime target 'libmsip0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmsip0']
NOTE: Runtime target 'libmikey0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmikey0']
NOTE: Runtime target 'xmu' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xmu']
NOTE: Runtime target 'evas-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['evas-fb']
NOTE: Runtime target 'esmart-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['esmart-fb']
NOTE: Runtime target 'imlib2-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['imlib2-fb']
NOTE: Runtime target 'efl++-fb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['efl++-fb']
NOTE: Runtime target 'codec-engine' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['codec-engine']
NOTE: Runtime target 'sword' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['sword']
NOTE: Runtime target 'clutter-0.6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['clutter-0.6']
NOTE: Runtime target 'libmnetutil0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libmnetutil0']
NOTE: Runtime target 'xdamage' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xdamage']
NOTE: Runtime target 'bluez-cups-backend' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-cups-backend',
'bluez-libs-3.36']
NOTE: Runtime target 'bluez-gstreamer-plugin' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-gstreamer-plugin',
'bluez-libs-3.36']
NOTE: Runtime target 'bluez-utils-alsa' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-alsa',
'bluez-libs-3.36']
NOTE: Runtime target 'ti-codec-engine-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-codec-engine-sdk']
NOTE: Runtime target 'task-arago-toolchain-dvsdk-host' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['task-arago-toolchain-dvsdk-host', 'ti-codec-engine-sdk']
NOTE: Runtime target 'ti-codec-combo-omap3530-sdk' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['ti-codec-combo-omap3530-sdk']
NOTE: Runtime target 'ti-xdctools-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-xdctools-sdk']
NOTE: Runtime target 'ti-dmai-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-dmai-sdk']
NOTE: Runtime target 'ti-dspbios-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-dspbios-sdk']
NOTE: Runtime target 'ti-cgt6x-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-cgt6x-sdk']
NOTE: Runtime target 'ti-legacy-dvsdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ti-legacy-dvsdk']
NOTE: Runtime target 'etk-native' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['etk-native']
NOTE: Runtime target 'bluez-libs-3.36' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-libs-3.36']

Same question as before: what are we doing with these recipes?
fix? (who?) ignore? move to non-buildable dir? remove ?
Opinions wanted


multiple providers:
==============

NOTE: multiple providers are available for bluez-utils-dbus (bluez4,
bluez-cups-backend, bluez-gstreamer-plugin, bluez-utils-alsa)
NOTE: multiple providers are available for wxwidgets (wxwidgets,
wxwidgets-opengl, wxwidgets-ansi)
NOTE: multiple providers are available for runtime e-wm-menu (e-wm,
menu-freesmartphone)
NOTE: multiple providers are available for runtime x11vnc (x11vnc,
libvncserver)
NOTE: multiple providers are available for runtime gnash-browser-plugin
(gnash, gnash-fb)
NOTE: multiple providers are available for runtime arora-data (arora-e,
arora)
NOTE: multiple providers are available for runtime java2-runtime (cacao,
jamvm, openjdk-6-jre)
NOTE: multiple providers are available for runtime gst-plugin-avi
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-matroska
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-mpegstream
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-mpegaudioparse
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-mpegvideoparse
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-mpeg2dec
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-playbin
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-decodebin
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-volume
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-audioconvert
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-audioresample
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime
gst-plugin-typefindfunctions (gst-plugins-bad, gst-plugins-good,
gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-autodetect
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-debug
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-audiotestsrc
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-videotestsrc
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-ivorbisdec
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-ogg
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-mad
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-id3demux
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-wavparse
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-gnomevfs
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-alsa
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-ximagesink
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-videoscale
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-videorate
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime
gst-plugin-ffmpegcolorspace (gst-plugins-bad, gst-plugins-good,
gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime abiword (abiword,
abiword-embedded)
NOTE: multiple providers are available for runtime libstdc++-dev (gcc,
external-toolchain-csl, external-toolchain-generic, external-toolchain)
NOTE: multiple providers are available for runtime gst-plugins-base-meta
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugins-good-meta
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugins-bad-meta
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugins-ugly-meta
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime esd (esound, osso-esd)
NOTE: multiple providers are available for runtime libltdl (libtool-sdk,
libtool)
NOTE: multiple providers are available for runtime module-init-tools-depmod
(module-init-tools, module-init-tools-cross)
NOTE: multiple providers are available for runtime xcursor-transparent-theme
(xcursor-transparent-theme, xcursor-watchonly-theme)
NOTE: multiple providers are available for runtime hotplug (udev,
hotplug-ng, linux-hotplug)
NOTE: multiple providers are available for runtime gdbserver (gdbserver,
gdb)
NOTE: multiple providers are available for runtime libmysqlclient-dev
(mysql5, mysql)
NOTE: multiple providers are available for runtime gst-plugin-dvb
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime libltdl-dev (libtool-sdk,
libtool)
NOTE: multiple providers are available for runtime abiword-plugin-collab
(abiword, abiword-plugins)
NOTE: multiple providers are available for runtime libmysqlclient (mysql5,
mysql)
NOTE: multiple providers are available for runtime gst-plugin-app
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-video4linux2
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime e-wm-sysactions (e-wm,
e-wm-sysactions-shr)
NOTE: multiple providers are available for runtime lxsession-lite
(lxsession-lite, lxsession)
NOTE: multiple providers are available for runtime virtual-japanese-font
(qpf-unismall, qpf-unifont)
NOTE: multiple providers are available for runtime busybox-static
(busybox-static, busybox)
NOTE: multiple providers are available for runtime xfwm4-theme-default
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime libpanel-applet
(gnome-panel, libgweather)
NOTE: multiple providers are available for runtime xserver-kdrive-fbdev
(xserver-kdrive, xserver-kdrive-1300)
NOTE: multiple providers are available for runtime
openmoko-sound-theme-standard (openmoko-sound-theme-standard,
openmoko-sound-theme-standard2)
NOTE: multiple providers are available for runtime dvbtraffic (dvbtraffic,
dvb-apps)
NOTE: multiple providers are available for runtime libgcc-dev (gcc,
external-toolchain-csl, external-toolchain-generic, external-toolchain)
NOTE: multiple providers are available for runtime bl (bl, gpe-conf)
NOTE: multiple providers are available for runtime gst-plugin-vorbis
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-decodebin2
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-xvimagesink
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-flv
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-nuvdemux
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-a52dec
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-ossaudio
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime midpath
(midpath-openmoko, midpath-maemo)
NOTE: multiple providers are available for runtime libfftw3 (fftw, fftwl,
fftwf)
NOTE: multiple providers are available for runtime openmoko-sound-system
(openmoko-sound-system, openmoko-sound-system2)
NOTE: multiple providers are available for runtime gst-plugins
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-audio
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-audiofile
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-esd
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-tagedit
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-ivorbis
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-tcp
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-schroedinger
(gst-plugin-schroedinger, schroedinger)
NOTE: multiple providers are available for runtime xfwm4-theme-daloa
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-moheli
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-default-4.0
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-default-4.2
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-default-4.4
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-kokodi
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-sassandra
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-stoneage
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-therapy
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-tyrex
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime xfwm4-theme-wallis
(xfwm4-themes, xfwm4)
NOTE: multiple providers are available for runtime dialog-static
(dialog-static, dialog)
NOTE: multiple providers are available for runtime gst-plugin-flac
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-souphttpsrc
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-mms
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-modplug
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime gst-plugin-sid
(gst-plugins-bad, gst-plugins-good, gst-plugins-base, gst-plugins-ugly)
NOTE: multiple providers are available for runtime frameworkd-config
(frameworkd-config-shr, frameworkd)
NOTE: multiple providers are available for runtime xserver-kdrive
(xserver-kdrive, xserver-kdrive-1300)

Some of these are quite explainable, but there are also some where I
seriously question why they exist.
Some cleaning seems desirable


I would like to see some discussion on how to move forward with this.

As I write the build is still running. When done I'll report back with a
list of recipes that are not buildable (but guess that will take a day or
so)

Frans.


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-29  8:50 OE recipe tree quality Frans Meulenbroeks
@ 2010-07-29  9:42 ` Thomas Zimmermann
  2010-07-29  9:45 ` Koen Kooi
  1 sibling, 0 replies; 23+ messages in thread
From: Thomas Zimmermann @ 2010-07-29  9:42 UTC (permalink / raw)
  To: openembedded-devel

Am Donnerstag 29 Juli 2010, 10:50:53 schrieb Frans Meulenbroeks:
> Dear all,
> 
> Given the discussions on quality that sometimes pop up (and also triggered
> by Robert's message), I decided to kick off a bitbake -k world.
> Below are some initial findings. I would like to use this as a starter to
> kickoff the discusson on quality and what to do with broken stuff.
> And also I hope that people who feel attached to a recipe mentioned below
> will take action.
> 
> My setting:
> local.conf:
> IMAGE_LINGUAS = ""
> ENABLE_BINARY_LOCALE_GENERATION = "0"
> 
> MACHINE = "beagleboard"
> DISTRO = "angstrom-2008.1"
> 
> EXTRA_IMAGECMD_jffs2 = "--pad --eraseblock=0x20000"
> MKUBIFS_ARGS = "-m 2048 -e 129024 -c 1024"
> 
> IMAGE_FSTYPES = "tar squashfs ubifs jffs2"
> IMAGE_KEEPROOTFS = "1"
> OE_ALLOW_INSECURE_DOWNLOADS = "yes"
> 
> I opted for angstromg and beagleboard as I feel this is the most often
> build configuration, so it should have the least issues.
> host is ubuntu 10.04 on 64 bit. tree is oe dev git head (as of jul 29)
> 
> All results are not in yet (there are 71047 taksks, I am at 159 :-)
> However the parsing already gave some interesting output.
> I've ordered them somehwat:
> 
> Nothing PROVIDES errors
> ===================
> ...
Some of these 'Nothing PROVIDES' errors are because you are using angstrom as 
distro and some recipes are blacklisted there (e.g. fso-apm), because of that 
a lot of the shr specific recipes aren't buildable.

I think one should do such a test with minimal distro because nothing is 
blacklisted there.

Other recipes like etk or epsilon were moved to obsolete, but recipes 
depending on them weren't. So i think recipes depending on etk and epsilon can 
be moved to obsolete too.

Regards
Thomas



^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-29  8:50 OE recipe tree quality Frans Meulenbroeks
  2010-07-29  9:42 ` Thomas Zimmermann
@ 2010-07-29  9:45 ` Koen Kooi
  2010-07-29 10:32   ` Frans Meulenbroeks
  2010-07-29 12:07   ` Philip Balister
  1 sibling, 2 replies; 23+ messages in thread
From: Koen Kooi @ 2010-07-29  9:45 UTC (permalink / raw)
  To: openembedded-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29-07-10 10:50, Frans Meulenbroeks wrote:
> Dear all,
> 
> Given the discussions on quality that sometimes pop up (and also triggered
> by Robert's message), I decided to kick off a bitbake -k world.

Could you first explain to me why 'bitbake world' is a good way to
measure quality?

I would think that building something like console-image and looking at
the following would be a much better metric:

* does it build?
* are all the rootfs types working?
* does the image do what it is supposed to do?
* Are all the licenses of the output packages correct?
* Do the output packages have any spurious deps?
* Is the content of the output packages correct?
* Are there any known CVEs in the resulting packages?
* Did packaged-staging do its job?
* What kind of QA errors and warnings were raised?
* Did all recipes pass recipe_sanity?
* Did all recipes conform to oe-stylize.py?

etc

I would actually advocate removing the 'world' feature from bitbake/OE
to stop people from wasting time on looking at bitbake world and have
them fix actual problems.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMUU3HMkyGM64RGpERAgioAJ90DxRRG5meARUBbMcQ25jadn4k4QCeKkEd
r4DWO6n6DTFhAucGqx78Yxc=
=Dv4L
-----END PGP SIGNATURE-----




^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-29  9:45 ` Koen Kooi
@ 2010-07-29 10:32   ` Frans Meulenbroeks
  2010-07-29 12:07   ` Philip Balister
  1 sibling, 0 replies; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-29 10:32 UTC (permalink / raw)
  To: openembedded-devel

Wrt the message of Thomas and the blacklisting
Maybe I'll try minimal later on.

Wrt Koen's message, see below:

2010/7/29 Koen Kooi <k.kooi@student.utwente.nl>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29-07-10 10:50, Frans Meulenbroeks wrote:
> > Dear all,
> >
> > Given the discussions on quality that sometimes pop up (and also
> triggered
> > by Robert's message), I decided to kick off a bitbake -k world.
>
> Could you first explain to me why 'bitbake world' is a good way to
> measure quality?


> I would think that building something like console-image and looking at
> the following would be a much better metric:
>
> * does it build?
> * are all the rootfs types working?
> * does the image do what it is supposed to do?
> * Are all the licenses of the output packages correct?
> * Do the output packages have any spurious deps?
> * Is the content of the output packages correct?
> * Are there any known CVEs in the resulting packages?
> * Did packaged-staging do its job?
> * What kind of QA errors and warnings were raised?
> * Did all recipes pass recipe_sanity?
> * Did all recipes conform to oe-stylize.py?
>

That is a fine set of criteria, but the focus of this exercise is not to
look at the recipes that are often build and that work.
What I want is buildable recipes. A recipe that does not build in my opinion
is useless and should either be fixed or removed.

There is a lot of crud in recipes, and the objective of this exercise was to
identify what junk there is around there and call for action on it.
You probably do not care if there is a non-buildable recipe around, but I
(and I guess others) do.

We as openembedded deliver a set of recipes. If a substantial amount of
recipes does not build that gives a bad perception of the quality of the
environment.
Apart from I perceive every non-buildable recipe as a bug.

My two cents...

>
> etc
>
> I would actually advocate removing the 'world' feature from bitbake/OE
> to stop people from wasting time on looking at bitbake world and have
> them fix actual problems.
>

Yeah. Shoot the messenger and hide the problem under the carpet.

For me removing world from bitbake/OE would be a no no.

And I must say that I am kind a surprised that you don't consider a non
buildable recipe as an actual problem.
I (and I hope others as well) do.

And wrt time:
Fortunately it is up to me  and not up to you to decide on how I waste my
time (even though in this case I do not feel it wasted, and the actual
amount of time invested in it is pretty small, it are mostly unused CPU
cycles that are used up by this).

Enjoy!
Frans.

>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMUU3HMkyGM64RGpERAgioAJ90DxRRG5meARUBbMcQ25jadn4k4QCeKkEd
> r4DWO6n6DTFhAucGqx78Yxc=
> =Dv4L
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-29  9:45 ` Koen Kooi
  2010-07-29 10:32   ` Frans Meulenbroeks
@ 2010-07-29 12:07   ` Philip Balister
  2010-07-29 12:15     ` Frans Meulenbroeks
  2010-07-30  7:21     ` Esben Haabendal
  1 sibling, 2 replies; 23+ messages in thread
From: Philip Balister @ 2010-07-29 12:07 UTC (permalink / raw)
  To: openembedded-devel



On 07/29/2010 05:45 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>> Dear all,
>>
>> Given the discussions on quality that sometimes pop up (and also triggered
>> by Robert's message), I decided to kick off a bitbake -k world.
>
> Could you first explain to me why 'bitbake world' is a good way to
> measure quality?
>
> I would think that building something like console-image and looking at
> the following would be a much better metric:
>
> * does it build?
> * are all the rootfs types working?
> * does the image do what it is supposed to do?
> * Are all the licenses of the output packages correct?
> * Do the output packages have any spurious deps?
> * Is the content of the output packages correct?
> * Are there any known CVEs in the resulting packages?
> * Did packaged-staging do its job?
> * What kind of QA errors and warnings were raised?
> * Did all recipes pass recipe_sanity?
> * Did all recipes conform to oe-stylize.py?
>
> etc
>
> I would actually advocate removing the 'world' feature from bitbake/OE
> to stop people from wasting time on looking at bitbake world and have
> them fix actual problems.

bitbake world seems to be the source of pointless listserv discussions. 
Does it serve any purpose?

Philip



^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-29 12:07   ` Philip Balister
@ 2010-07-29 12:15     ` Frans Meulenbroeks
  2010-07-30  7:21     ` Esben Haabendal
  1 sibling, 0 replies; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-29 12:15 UTC (permalink / raw)
  To: openembedded-devel

2010/7/29 Philip Balister <philip@balister.org>

>
>
> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>>
>>> Dear all,
>>>
>>> Given the discussions on quality that sometimes pop up (and also
>>> triggered
>>> by Robert's message), I decided to kick off a bitbake -k world.
>>>
>>
>> Could you first explain to me why 'bitbake world' is a good way to
>> measure quality?
>>
>> I would think that building something like console-image and looking at
>> the following would be a much better metric:
>>
>> * does it build?
>> * are all the rootfs types working?
>> * does the image do what it is supposed to do?
>> * Are all the licenses of the output packages correct?
>> * Do the output packages have any spurious deps?
>> * Is the content of the output packages correct?
>> * Are there any known CVEs in the resulting packages?
>> * Did packaged-staging do its job?
>> * What kind of QA errors and warnings were raised?
>> * Did all recipes pass recipe_sanity?
>> * Did all recipes conform to oe-stylize.py?
>>
>> etc
>>
>> I would actually advocate removing the 'world' feature from bitbake/OE
>> to stop people from wasting time on looking at bitbake world and have
>> them fix actual problems.
>>
>
> bitbake world seems to be the source of pointless listserv discussions.
> Does it serve any purpose?
>

If you feel that in principle every recipe should be buildable, I'd say yes.
Also ideally bitbake -g world should give you a nice list of dependencies
allowing you to find out who the actual users of a recipe are.
But unfortunately last time I tried that it didn't work because of broken
dependencies or so.

Frans


>
> Philip
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-29 12:07   ` Philip Balister
  2010-07-29 12:15     ` Frans Meulenbroeks
@ 2010-07-30  7:21     ` Esben Haabendal
  2010-07-30  8:22       ` Koen Kooi
  1 sibling, 1 reply; 23+ messages in thread
From: Esben Haabendal @ 2010-07-30  7:21 UTC (permalink / raw)
  To: openembedded-devel

On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister <philip@balister.org> wrote:
>
>
> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>>>
>>> Dear all,
>>>
>>> Given the discussions on quality that sometimes pop up (and also
>>> triggered
>>> by Robert's message), I decided to kick off a bitbake -k world.
>>
>> Could you first explain to me why 'bitbake world' is a good way to
>> measure quality?
>>
>> I would think that building something like console-image and looking at
>> the following would be a much better metric:
>>
>> * does it build?
>> * are all the rootfs types working?
>> * does the image do what it is supposed to do?
>> * Are all the licenses of the output packages correct?
>> * Do the output packages have any spurious deps?
>> * Is the content of the output packages correct?
>> * Are there any known CVEs in the resulting packages?
>> * Did packaged-staging do its job?
>> * What kind of QA errors and warnings were raised?
>> * Did all recipes pass recipe_sanity?
>> * Did all recipes conform to oe-stylize.py?
>>
>> etc
>>
>> I would actually advocate removing the 'world' feature from bitbake/OE
>> to stop people from wasting time on looking at bitbake world and have
>> them fix actual problems.
>
> bitbake world seems to be the source of pointless listserv discussions. Does
> it serve any purpose?

Pointless or not really depends on how you look at quality.

If you look at it as you, Koen and other OE long-timers, yes, it looks
rather pointless to have bitbake world.
But for those of us who have a different view on what quality is, then
bitbake world serves a purpose.
It can be used to get a rough picture of the current quality, and if
it were accepted, even use it to clean up OE and thus raise the
quality according to our quality measurement.

So the actual discussion that is popping up (again), what the common
quality goals for OE is.
And that should hopefully not be seen as a pointless discussion.
Hopefully, it will be a continous discussion, from now on and forever.

/Esben
-- 
Esben Haabendal, Senior Software Consultant
DoréDevelopment ApS, Ved Stranden 1, 9560 Hadsund, DK-Denmark
Phone: +45 51 92 53 93, E-mail: eha@doredevelopment.dk
WWW: http://www.doredevelopment.dk



^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  7:21     ` Esben Haabendal
@ 2010-07-30  8:22       ` Koen Kooi
  2010-07-30  8:31         ` Graeme Gregory
  2010-07-30  8:34         ` Frans Meulenbroeks
  0 siblings, 2 replies; 23+ messages in thread
From: Koen Kooi @ 2010-07-30  8:22 UTC (permalink / raw)
  To: openembedded-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30-07-10 09:21, Esben Haabendal wrote:
> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister <philip@balister.org> wrote:
>>
>>
>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>>>>
>>>> Dear all,
>>>>
>>>> Given the discussions on quality that sometimes pop up (and also
>>>> triggered
>>>> by Robert's message), I decided to kick off a bitbake -k world.
>>>
>>> Could you first explain to me why 'bitbake world' is a good way to
>>> measure quality?
>>>
>>> I would think that building something like console-image and looking at
>>> the following would be a much better metric:
>>>
>>> * does it build?
>>> * are all the rootfs types working?
>>> * does the image do what it is supposed to do?
>>> * Are all the licenses of the output packages correct?
>>> * Do the output packages have any spurious deps?
>>> * Is the content of the output packages correct?
>>> * Are there any known CVEs in the resulting packages?
>>> * Did packaged-staging do its job?
>>> * What kind of QA errors and warnings were raised?
>>> * Did all recipes pass recipe_sanity?
>>> * Did all recipes conform to oe-stylize.py?
>>>
>>> etc
>>>
>>> I would actually advocate removing the 'world' feature from bitbake/OE
>>> to stop people from wasting time on looking at bitbake world and have
>>> them fix actual problems.
>>
>> bitbake world seems to be the source of pointless listserv discussions. Does
>> it serve any purpose?
> 
> Pointless or not really depends on how you look at quality.
> 
> If you look at it as you, Koen and other OE long-timers, yes, it looks
> rather pointless to have bitbake world.
> But for those of us who have a different view on what quality is, then
> bitbake world serves a purpose.

As Thomas points out, as soon as you start blacklisting things (which
actually increases quality), bitbake world doesn't work anymore.
That alone should be enough to kill it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMUouuMkyGM64RGpERAl42AKCE62tZc4ZGAH5WiLMPFNwn/YY0cACfTmMz
/YBK4XU/u1PuqmzoyXbF1f8=
=TNJJ
-----END PGP SIGNATURE-----




^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:22       ` Koen Kooi
@ 2010-07-30  8:31         ` Graeme Gregory
  2010-07-30  8:48           ` Frans Meulenbroeks
  2010-07-30  8:54           ` Esben Haabendal
  2010-07-30  8:34         ` Frans Meulenbroeks
  1 sibling, 2 replies; 23+ messages in thread
From: Graeme Gregory @ 2010-07-30  8:31 UTC (permalink / raw)
  To: openembedded-devel

 On 30/07/10 09:22, Koen Kooi wrote:
> On 30-07-10 09:21, Esben Haabendal wrote:
> > On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister
> <philip@balister.org> wrote:
> >>
> >>
> >> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> >>>
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
> >>>>
> >>>> Dear all,
> >>>>
> >>>> Given the discussions on quality that sometimes pop up (and also
> >>>> triggered
> >>>> by Robert's message), I decided to kick off a bitbake -k world.
> >>>
> >>> Could you first explain to me why 'bitbake world' is a good way to
> >>> measure quality?
> >>>
> >>> I would think that building something like console-image and
> looking at
> >>> the following would be a much better metric:
> >>>
> >>> * does it build?
> >>> * are all the rootfs types working?
> >>> * does the image do what it is supposed to do?
> >>> * Are all the licenses of the output packages correct?
> >>> * Do the output packages have any spurious deps?
> >>> * Is the content of the output packages correct?
> >>> * Are there any known CVEs in the resulting packages?
> >>> * Did packaged-staging do its job?
> >>> * What kind of QA errors and warnings were raised?
> >>> * Did all recipes pass recipe_sanity?
> >>> * Did all recipes conform to oe-stylize.py?
> >>>
> >>> etc
> >>>
> >>> I would actually advocate removing the 'world' feature from bitbake/OE
> >>> to stop people from wasting time on looking at bitbake world and have
> >>> them fix actual problems.
> >>
> >> bitbake world seems to be the source of pointless listserv
> discussions. Does
> >> it serve any purpose?
>
> > Pointless or not really depends on how you look at quality.
>
> > If you look at it as you, Koen and other OE long-timers, yes, it looks
> > rather pointless to have bitbake world.
> > But for those of us who have a different view on what quality is, then
> > bitbake world serves a purpose.
>
> As Thomas points out, as soon as you start blacklisting things (which
> actually increases quality), bitbake world doesn't work anymore.
> That alone should be enough to kill it.
Time to jump in the cage here.

"Quality" is achieved by comparing a set of known specifications against
a known data set. In the software case this means we need a good set of
specifications which we are testing against. We also need to know in
detail what we are testing against this set of specifications.

bitbake world meets neither of these criteria. You have no idea what
your testing against, you also have no idea what you are submitting for
test. A random selection of 8500 files in OE. It also doesn't take into
account known combinations which always fail. Angstrom took care of
these known failures by creating the concept of a blacklist.

In fact if you tell me bitbake world fails, I would actually suggest
that is a test pass, it is an expected fail.

Graeme





^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:22       ` Koen Kooi
  2010-07-30  8:31         ` Graeme Gregory
@ 2010-07-30  8:34         ` Frans Meulenbroeks
  2010-07-30  8:41           ` Koen Kooi
  2010-07-31 23:12           ` Richard Purdie
  1 sibling, 2 replies; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-30  8:34 UTC (permalink / raw)
  To: openembedded-devel

2010/7/30 Koen Kooi <k.kooi@student.utwente.nl>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 30-07-10 09:21, Esben Haabendal wrote:
> > On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister <philip@balister.org>
> wrote:
> >>
> >>
> >> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> >>>
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
> >>>>
> >>>> Dear all,
> >>>>
> >>>> Given the discussions on quality that sometimes pop up (and also
> >>>> triggered
> >>>> by Robert's message), I decided to kick off a bitbake -k world.
> >>>
> >>> Could you first explain to me why 'bitbake world' is a good way to
> >>> measure quality?
> >>>
> >>> I would think that building something like console-image and looking at
> >>> the following would be a much better metric:
> >>>
> >>> * does it build?
> >>> * are all the rootfs types working?
> >>> * does the image do what it is supposed to do?
> >>> * Are all the licenses of the output packages correct?
> >>> * Do the output packages have any spurious deps?
> >>> * Is the content of the output packages correct?
> >>> * Are there any known CVEs in the resulting packages?
> >>> * Did packaged-staging do its job?
> >>> * What kind of QA errors and warnings were raised?
> >>> * Did all recipes pass recipe_sanity?
> >>> * Did all recipes conform to oe-stylize.py?
> >>>
> >>> etc
> >>>
> >>> I would actually advocate removing the 'world' feature from bitbake/OE
> >>> to stop people from wasting time on looking at bitbake world and have
> >>> them fix actual problems.
> >>
> >> bitbake world seems to be the source of pointless listserv discussions.
> Does
> >> it serve any purpose?
> >
> > Pointless or not really depends on how you look at quality.
> >
> > If you look at it as you, Koen and other OE long-timers, yes, it looks
> > rather pointless to have bitbake world.
> > But for those of us who have a different view on what quality is, then
> > bitbake world serves a purpose.
>
> As Thomas points out, as soon as you start blacklisting things (which
> actually increases quality), bitbake world doesn't work anymore.
>

Blacklisting does *NOT* increase quality. It just hides the problem and as
such it is ostrich behaviour.

Instead of masking the problem, better fix things. That is what improves
quality!

For me a non building recipe is a sign of poor quality.

BTW: to avoid the blacklisting issue, I've restarted my test with minimal
distro.
Results will probably be available after the weekend.

Frans.



> That alone should be enough to kill it.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMUouuMkyGM64RGpERAl42AKCE62tZc4ZGAH5WiLMPFNwn/YY0cACfTmMz
> /YBK4XU/u1PuqmzoyXbF1f8=
> =TNJJ
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:34         ` Frans Meulenbroeks
@ 2010-07-30  8:41           ` Koen Kooi
  2010-07-30  9:01             ` Frans Meulenbroeks
  2010-07-31 23:12           ` Richard Purdie
  1 sibling, 1 reply; 23+ messages in thread
From: Koen Kooi @ 2010-07-30  8:41 UTC (permalink / raw)
  To: openembedded-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30-07-10 10:34, Frans Meulenbroeks wrote:
> 2010/7/30 Koen Kooi <k.kooi@student.utwente.nl>
> 
> On 30-07-10 09:21, Esben Haabendal wrote:
>>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister <philip@balister.org>
> wrote:
>>>>>
>>>>>
>>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>>>>>>
>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>>>>>>>
>>>>>>> Dear all,
>>>>>>>
>>>>>>> Given the discussions on quality that sometimes pop up (and also
>>>>>>> triggered
>>>>>>> by Robert's message), I decided to kick off a bitbake -k world.
>>>>>>
>>>>>> Could you first explain to me why 'bitbake world' is a good way to
>>>>>> measure quality?
>>>>>>
>>>>>> I would think that building something like console-image and looking at
>>>>>> the following would be a much better metric:
>>>>>>
>>>>>> * does it build?
>>>>>> * are all the rootfs types working?
>>>>>> * does the image do what it is supposed to do?
>>>>>> * Are all the licenses of the output packages correct?
>>>>>> * Do the output packages have any spurious deps?
>>>>>> * Is the content of the output packages correct?
>>>>>> * Are there any known CVEs in the resulting packages?
>>>>>> * Did packaged-staging do its job?
>>>>>> * What kind of QA errors and warnings were raised?
>>>>>> * Did all recipes pass recipe_sanity?
>>>>>> * Did all recipes conform to oe-stylize.py?
>>>>>>
>>>>>> etc
>>>>>>
>>>>>> I would actually advocate removing the 'world' feature from bitbake/OE
>>>>>> to stop people from wasting time on looking at bitbake world and have
>>>>>> them fix actual problems.
>>>>>
>>>>> bitbake world seems to be the source of pointless listserv discussions.
> Does
>>>>> it serve any purpose?
>>>>
>>>> Pointless or not really depends on how you look at quality.
>>>>
>>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
>>>> rather pointless to have bitbake world.
>>>> But for those of us who have a different view on what quality is, then
>>>> bitbake world serves a purpose.
> 
> As Thomas points out, as soon as you start blacklisting things (which
> actually increases quality), bitbake world doesn't work anymore.
> 
> 
>> Blacklisting does *NOT* increase quality. It just hides the problem and as
>> such it is ostrich behaviour.

You're saying that making a choice to only support bluez4 and disallow
linking to random bluez versions does not increase quality? The bluez
people are quite clear on this, pick a version and stick with it.
So please explain to me why following upstream advice and making things
deterministic doesn't increase quality?
You seem to be implying that the bluez developers are a bunch of
ostriches for keeping the API compatible, no?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMUpAcMkyGM64RGpERAjsTAJ4mtLOVTbW/j/YvrAUfMgJbFmKPDQCfTz9b
D9h1U+Cqg3L9yC3CheQSYr8=
=Nj6f
-----END PGP SIGNATURE-----




^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:31         ` Graeme Gregory
@ 2010-07-30  8:48           ` Frans Meulenbroeks
  2010-07-30  8:56             ` Graeme Gregory
  2010-07-30  8:54           ` Esben Haabendal
  1 sibling, 1 reply; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-30  8:48 UTC (permalink / raw)
  To: openembedded-devel

2010/7/30 Graeme Gregory <dp@xora.org.uk>

>  On 30/07/10 09:22, Koen Kooi wrote:
> > On 30-07-10 09:21, Esben Haabendal wrote:
> > > On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister
> > <philip@balister.org> wrote:
> > >>
> > >>
> > >> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> > >>>
> > >>> -----BEGIN PGP SIGNED MESSAGE-----
> > >>> Hash: SHA1
> > >>>
> > >>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
> > >>>>
> > >>>> Dear all,
> > >>>>
> > >>>> Given the discussions on quality that sometimes pop up (and also
> > >>>> triggered
> > >>>> by Robert's message), I decided to kick off a bitbake -k world.
> > >>>
> > >>> Could you first explain to me why 'bitbake world' is a good way to
> > >>> measure quality?
> > >>>
> > >>> I would think that building something like console-image and
> > looking at
> > >>> the following would be a much better metric:
> > >>>
> > >>> * does it build?
> > >>> * are all the rootfs types working?
> > >>> * does the image do what it is supposed to do?
> > >>> * Are all the licenses of the output packages correct?
> > >>> * Do the output packages have any spurious deps?
> > >>> * Is the content of the output packages correct?
> > >>> * Are there any known CVEs in the resulting packages?
> > >>> * Did packaged-staging do its job?
> > >>> * What kind of QA errors and warnings were raised?
> > >>> * Did all recipes pass recipe_sanity?
> > >>> * Did all recipes conform to oe-stylize.py?
> > >>>
> > >>> etc
> > >>>
> > >>> I would actually advocate removing the 'world' feature from
> bitbake/OE
> > >>> to stop people from wasting time on looking at bitbake world and have
> > >>> them fix actual problems.
> > >>
> > >> bitbake world seems to be the source of pointless listserv
> > discussions. Does
> > >> it serve any purpose?
> >
> > > Pointless or not really depends on how you look at quality.
> >
> > > If you look at it as you, Koen and other OE long-timers, yes, it looks
> > > rather pointless to have bitbake world.
> > > But for those of us who have a different view on what quality is, then
> > > bitbake world serves a purpose.
> >
> > As Thomas points out, as soon as you start blacklisting things (which
> > actually increases quality), bitbake world doesn't work anymore.
> > That alone should be enough to kill it.
> Time to jump in the cage here.
>
> "Quality" is achieved by comparing a set of known specifications against
> a known data set. In the software case this means we need a good set of
> specifications which we are testing against. We also need to know in
> detail what we are testing against this set of specifications.
>
> bitbake world meets neither of these criteria. You have no idea what
> your testing against, you also have no idea what you are submitting for
> test. A random selection of 8500 files in OE. It also doesn't take into
> account known combinations which always fail. Angstrom took care of
> these known failures by creating the concept of a blacklist.
>
> In fact if you tell me bitbake world fails, I would actually suggest
> that is a test pass, it is an expected fail.
>
> Graeme
>
> Actually I expect it to fail, but I am eager to learn which recipes fail.
And yes, it might well be that this is not a good test. If you have
suggestions for a better test that tests all our recipes feel free to speak
up.

The dependency analysis of bitbake world already showed that there are
several issues (as listed above).
E.g. there are apparently dependencies on non existing recipes.
Instead of shooting the messenger and killing the tool it would be better
to  resolve these (by either fixing them as I have seen JaMa did for some
recipes in the past) or by removing the recipes.
Keeping them around as junk does not improve things.

And failure of bitbake -k world is not necessarily bad. At least it will
give some insight in the weak spots.

Frans.


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:31         ` Graeme Gregory
  2010-07-30  8:48           ` Frans Meulenbroeks
@ 2010-07-30  8:54           ` Esben Haabendal
  1 sibling, 0 replies; 23+ messages in thread
From: Esben Haabendal @ 2010-07-30  8:54 UTC (permalink / raw)
  To: openembedded-devel

On Fri, Jul 30, 2010 at 10:31 AM, Graeme Gregory <dp@xora.org.uk> wrote:
>  On 30/07/10 09:22, Koen Kooi wrote:
>> On 30-07-10 09:21, Esben Haabendal wrote:
>> > On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister
>> <philip@balister.org> wrote:
>> >>
>> >>
>> >> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>> >>>
>> >>> -----BEGIN PGP SIGNED MESSAGE-----
>> >>> Hash: SHA1
>> >>>
>> >>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>> >>>>
>> >>>> Dear all,
>> >>>>
>> >>>> Given the discussions on quality that sometimes pop up (and also
>> >>>> triggered
>> >>>> by Robert's message), I decided to kick off a bitbake -k world.
>> >>>
>> >>> Could you first explain to me why 'bitbake world' is a good way to
>> >>> measure quality?
>> >>>
>> >>> I would think that building something like console-image and
>> looking at
>> >>> the following would be a much better metric:
>> >>>
>> >>> * does it build?
>> >>> * are all the rootfs types working?
>> >>> * does the image do what it is supposed to do?
>> >>> * Are all the licenses of the output packages correct?
>> >>> * Do the output packages have any spurious deps?
>> >>> * Is the content of the output packages correct?
>> >>> * Are there any known CVEs in the resulting packages?
>> >>> * Did packaged-staging do its job?
>> >>> * What kind of QA errors and warnings were raised?
>> >>> * Did all recipes pass recipe_sanity?
>> >>> * Did all recipes conform to oe-stylize.py?
>> >>>
>> >>> etc
>> >>>
>> >>> I would actually advocate removing the 'world' feature from bitbake/OE
>> >>> to stop people from wasting time on looking at bitbake world and have
>> >>> them fix actual problems.
>> >>
>> >> bitbake world seems to be the source of pointless listserv
>> discussions. Does
>> >> it serve any purpose?
>>
>> > Pointless or not really depends on how you look at quality.
>>
>> > If you look at it as you, Koen and other OE long-timers, yes, it looks
>> > rather pointless to have bitbake world.
>> > But for those of us who have a different view on what quality is, then
>> > bitbake world serves a purpose.
>>
>> As Thomas points out, as soon as you start blacklisting things (which
>> actually increases quality), bitbake world doesn't work anymore.
>> That alone should be enough to kill it.
> Time to jump in the cage here.

Welcome :-)

> "Quality" is achieved by comparing a set of known specifications against
> a known data set. In the software case this means we need a good set of
> specifications which we are testing against. We also need to know in
> detail what we are testing against this set of specifications.

That is by no means the definitive definition of "Quality" in software.

From http://en.wikipedia.org/wiki/Software_quality : Another
definition, coined by Gerald Weinberg in Quality Software Management:
Systems Thinking, is "Quality is value to some person." This
definition stresses that quality is inherently subjective - different
people will experience the quality of the same software very
differently. One strength of this definition is the questions it
invites software teams to consider, such as "Who are the people we
want to value our software?" and "What will be valuable to them?"

We should not assume that a community such as OE will agree 100% of
what software quality is, but we have to agree on what type of
software quality definitions we will work towards.

I am happy to see that I am not completely alone with my views on what
could improve the software quality of OE, but at the same time I
respect the fact that a lot of the most active OE developers have
different views on software quality.

But I believe everybody should respect that there are different
opnions on what quality is, and none of them should have complete
monopoly, hence the need for a continous discussion on software
quality of OE.

/Esben



^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:48           ` Frans Meulenbroeks
@ 2010-07-30  8:56             ` Graeme Gregory
  2010-07-30  9:07               ` Frans Meulenbroeks
  0 siblings, 1 reply; 23+ messages in thread
From: Graeme Gregory @ 2010-07-30  8:56 UTC (permalink / raw)
  To: openembedded-devel

 On 30/07/10 09:48, Frans Meulenbroeks wrote:
> 2010/7/30 Graeme Gregory <dp@xora.org.uk>
>
>>  On 30/07/10 09:22, Koen Kooi wrote:
>>> On 30-07-10 09:21, Esben Haabendal wrote:
>>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister
>>> <philip@balister.org> wrote:
>>>>>
>>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>>>>>>> Dear all,
>>>>>>>
>>>>>>> Given the discussions on quality that sometimes pop up (and also
>>>>>>> triggered
>>>>>>> by Robert's message), I decided to kick off a bitbake -k world.
>>>>>> Could you first explain to me why 'bitbake world' is a good way to
>>>>>> measure quality?
>>>>>>
>>>>>> I would think that building something like console-image and
>>> looking at
>>>>>> the following would be a much better metric:
>>>>>>
>>>>>> * does it build?
>>>>>> * are all the rootfs types working?
>>>>>> * does the image do what it is supposed to do?
>>>>>> * Are all the licenses of the output packages correct?
>>>>>> * Do the output packages have any spurious deps?
>>>>>> * Is the content of the output packages correct?
>>>>>> * Are there any known CVEs in the resulting packages?
>>>>>> * Did packaged-staging do its job?
>>>>>> * What kind of QA errors and warnings were raised?
>>>>>> * Did all recipes pass recipe_sanity?
>>>>>> * Did all recipes conform to oe-stylize.py?
>>>>>>
>>>>>> etc
>>>>>>
>>>>>> I would actually advocate removing the 'world' feature from
>> bitbake/OE
>>>>>> to stop people from wasting time on looking at bitbake world and have
>>>>>> them fix actual problems.
>>>>> bitbake world seems to be the source of pointless listserv
>>> discussions. Does
>>>>> it serve any purpose?
>>>> Pointless or not really depends on how you look at quality.
>>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
>>>> rather pointless to have bitbake world.
>>>> But for those of us who have a different view on what quality is, then
>>>> bitbake world serves a purpose.
>>> As Thomas points out, as soon as you start blacklisting things (which
>>> actually increases quality), bitbake world doesn't work anymore.
>>> That alone should be enough to kill it.
>> Time to jump in the cage here.
>>
>> "Quality" is achieved by comparing a set of known specifications against
>> a known data set. In the software case this means we need a good set of
>> specifications which we are testing against. We also need to know in
>> detail what we are testing against this set of specifications.
>>
>> bitbake world meets neither of these criteria. You have no idea what
>> your testing against, you also have no idea what you are submitting for
>> test. A random selection of 8500 files in OE. It also doesn't take into
>> account known combinations which always fail. Angstrom took care of
>> these known failures by creating the concept of a blacklist.
>>
>> In fact if you tell me bitbake world fails, I would actually suggest
>> that is a test pass, it is an expected fail.
>>
>> Graeme
>>
>> Actually I expect it to fail, but I am eager to learn which recipes fail.
> And yes, it might well be that this is not a good test. If you have
> suggestions for a better test that tests all our recipes feel free to speak
> up.
>
> The dependency analysis of bitbake world already showed that there are
> several issues (as listed above).
> E.g. there are apparently dependencies on non existing recipes.
> Instead of shooting the messenger and killing the tool it would be better
> to  resolve these (by either fixing them as I have seen JaMa did for some
> recipes in the past) or by removing the recipes.
> Keeping them around as junk does not improve things.
>
> And failure of bitbake -k world is not necessarily bad. At least it will
> give some insight in the weak spots.
>
More interesting to me would be an algorithm more like.

while recipe in recips/*.bb; do
    rm -rf tmp/ ; bitbake recipe
done

with the test noting if the fail is due to a blacklisted dependency, a
totally missing dependency (recipe been deleted sometime in past) or an
actual compile fail due to a missing DEPENDS entry somewhere in the tree.

But this is going to burn CPU time like never before.

Graeme




^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:41           ` Koen Kooi
@ 2010-07-30  9:01             ` Frans Meulenbroeks
  2010-07-30 15:39               ` Dr. Michael Lauer
  0 siblings, 1 reply; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-30  9:01 UTC (permalink / raw)
  To: openembedded-devel

2010/7/30 Koen Kooi <k.kooi@student.utwente.nl>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 30-07-10 10:34, Frans Meulenbroeks wrote:
> > 2010/7/30 Koen Kooi <k.kooi@student.utwente.nl>
> >
> > On 30-07-10 09:21, Esben Haabendal wrote:
> >>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister <philip@balister.org
> >
> > wrote:
> >>>>>
> >>>>>
> >>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> >>>>>>
> >>>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>>> Hash: SHA1
> >>>>>>
> >>>>>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
> >>>>>>>
> >>>>>>> Dear all,
> >>>>>>>
> >>>>>>> Given the discussions on quality that sometimes pop up (and also
> >>>>>>> triggered
> >>>>>>> by Robert's message), I decided to kick off a bitbake -k world.
> >>>>>>
> >>>>>> Could you first explain to me why 'bitbake world' is a good way to
> >>>>>> measure quality?
> >>>>>>
> >>>>>> I would think that building something like console-image and looking
> at
> >>>>>> the following would be a much better metric:
> >>>>>>
> >>>>>> * does it build?
> >>>>>> * are all the rootfs types working?
> >>>>>> * does the image do what it is supposed to do?
> >>>>>> * Are all the licenses of the output packages correct?
> >>>>>> * Do the output packages have any spurious deps?
> >>>>>> * Is the content of the output packages correct?
> >>>>>> * Are there any known CVEs in the resulting packages?
> >>>>>> * Did packaged-staging do its job?
> >>>>>> * What kind of QA errors and warnings were raised?
> >>>>>> * Did all recipes pass recipe_sanity?
> >>>>>> * Did all recipes conform to oe-stylize.py?
> >>>>>>
> >>>>>> etc
> >>>>>>
> >>>>>> I would actually advocate removing the 'world' feature from
> bitbake/OE
> >>>>>> to stop people from wasting time on looking at bitbake world and
> have
> >>>>>> them fix actual problems.
> >>>>>
> >>>>> bitbake world seems to be the source of pointless listserv
> discussions.
> > Does
> >>>>> it serve any purpose?
> >>>>
> >>>> Pointless or not really depends on how you look at quality.
> >>>>
> >>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
> >>>> rather pointless to have bitbake world.
> >>>> But for those of us who have a different view on what quality is, then
> >>>> bitbake world serves a purpose.
> >
> > As Thomas points out, as soon as you start blacklisting things (which
> > actually increases quality), bitbake world doesn't work anymore.
> >
> >
> >> Blacklisting does *NOT* increase quality. It just hides the problem and
> as
> >> such it is ostrich behaviour.
>
> You're saying that making a choice to only support bluez4 and disallow
> linking to random bluez versions does not increase quality? The bluez
>

It increases the quality of the distro, not the overall quality of OE.


> people are quite clear on this, pick a version and stick with it.
>

You're hitting the nail on head with this. One of the problems of OE is that
we want to support too many versions at the same time.
dev head should not have two versions of bluez in the first place.
The development process should be that there are stable releases that are
used for production work and an unstable release or dev head that can be
used for further developments.
What is happening now is that people are abusing dev head and aim to use it
as production version which IMHO is bad.
dev head should aim at moving forward. E.g. latest stable could use bluez3
and dev head could then move to bluez4.

So please explain to me why following upstream advice and making things
> deterministic doesn't increase quality?
> You seem to be implying that the bluez developers are a bunch of
> ostriches for keeping the API compatible, no?
>

No, not at all. I know it is desirable to keep APIs compatible, and I also
know that sometimes there are reasons to break compatibility (and as an
inbetween there is upwards compatibility).
And for the record: I did not make any statement on bluez or its developers.

The problem is entirely at our side, by deciding to maintain multiple
variants of a package in dev head.

BTW and blacklisting is only a side observation on why things fail.
It would still be good to fix the dependency issues (and actually I would
but most of them seem to be in the maemo/openmoko/e17 area, an area where I
have neither expertise in nor hardware to test things).

Frans

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMUpAcMkyGM64RGpERAjsTAJ4mtLOVTbW/j/YvrAUfMgJbFmKPDQCfTz9b
> D9h1U+Cqg3L9yC3CheQSYr8=
> =Nj6f
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:56             ` Graeme Gregory
@ 2010-07-30  9:07               ` Frans Meulenbroeks
  2010-07-30  9:09                 ` Graeme Gregory
  2010-07-30  9:36                 ` Marcin Juszkiewicz
  0 siblings, 2 replies; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-07-30  9:07 UTC (permalink / raw)
  To: openembedded-devel

2010/7/30 Graeme Gregory <dp@xora.org.uk>

>  On 30/07/10 09:48, Frans Meulenbroeks wrote:
> > 2010/7/30 Graeme Gregory <dp@xora.org.uk>
> >
> >>  On 30/07/10 09:22, Koen Kooi wrote:
> >>> On 30-07-10 09:21, Esben Haabendal wrote:
> >>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister
> >>> <philip@balister.org> wrote:
> >>>>>
> >>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> >>>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>>> Hash: SHA1
> >>>>>>
> >>>>>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
> >>>>>>> Dear all,
> >>>>>>>
> >>>>>>> Given the discussions on quality that sometimes pop up (and also
> >>>>>>> triggered
> >>>>>>> by Robert's message), I decided to kick off a bitbake -k world.
> >>>>>> Could you first explain to me why 'bitbake world' is a good way to
> >>>>>> measure quality?
> >>>>>>
> >>>>>> I would think that building something like console-image and
> >>> looking at
> >>>>>> the following would be a much better metric:
> >>>>>>
> >>>>>> * does it build?
> >>>>>> * are all the rootfs types working?
> >>>>>> * does the image do what it is supposed to do?
> >>>>>> * Are all the licenses of the output packages correct?
> >>>>>> * Do the output packages have any spurious deps?
> >>>>>> * Is the content of the output packages correct?
> >>>>>> * Are there any known CVEs in the resulting packages?
> >>>>>> * Did packaged-staging do its job?
> >>>>>> * What kind of QA errors and warnings were raised?
> >>>>>> * Did all recipes pass recipe_sanity?
> >>>>>> * Did all recipes conform to oe-stylize.py?
> >>>>>>
> >>>>>> etc
> >>>>>>
> >>>>>> I would actually advocate removing the 'world' feature from
> >> bitbake/OE
> >>>>>> to stop people from wasting time on looking at bitbake world and
> have
> >>>>>> them fix actual problems.
> >>>>> bitbake world seems to be the source of pointless listserv
> >>> discussions. Does
> >>>>> it serve any purpose?
> >>>> Pointless or not really depends on how you look at quality.
> >>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
> >>>> rather pointless to have bitbake world.
> >>>> But for those of us who have a different view on what quality is, then
> >>>> bitbake world serves a purpose.
> >>> As Thomas points out, as soon as you start blacklisting things (which
> >>> actually increases quality), bitbake world doesn't work anymore.
> >>> That alone should be enough to kill it.
> >> Time to jump in the cage here.
> >>
> >> "Quality" is achieved by comparing a set of known specifications against
> >> a known data set. In the software case this means we need a good set of
> >> specifications which we are testing against. We also need to know in
> >> detail what we are testing against this set of specifications.
> >>
> >> bitbake world meets neither of these criteria. You have no idea what
> >> your testing against, you also have no idea what you are submitting for
> >> test. A random selection of 8500 files in OE. It also doesn't take into
> >> account known combinations which always fail. Angstrom took care of
> >> these known failures by creating the concept of a blacklist.
> >>
> >> In fact if you tell me bitbake world fails, I would actually suggest
> >> that is a test pass, it is an expected fail.
> >>
> >> Graeme
> >>
> >> Actually I expect it to fail, but I am eager to learn which recipes
> fail.
> > And yes, it might well be that this is not a good test. If you have
> > suggestions for a better test that tests all our recipes feel free to
> speak
> > up.
> >
> > The dependency analysis of bitbake world already showed that there are
> > several issues (as listed above).
> > E.g. there are apparently dependencies on non existing recipes.
> > Instead of shooting the messenger and killing the tool it would be better
> > to  resolve these (by either fixing them as I have seen JaMa did for some
> > recipes in the past) or by removing the recipes.
> > Keeping them around as junk does not improve things.
> >
> > And failure of bitbake -k world is not necessarily bad. At least it will
> > give some insight in the weak spots.
> >
> More interesting to me would be an algorithm more like.
>
> while recipe in recips/*.bb; do
>    rm -rf tmp/ ; bitbake recipe
> done
>
> with the test noting if the fail is due to a blacklisted dependency, a
> totally missing dependency (recipe been deleted sometime in past) or an
> actual compile fail due to a missing DEPENDS entry somewhere in the tree.
>
> But this is going to burn CPU time like never before.
>
> Graeme
>
>
Graeme,

Definitely an interesting test. Actually with packaged staging this might
become manageble.
I would not mind running such a test, even if it takes a week or so.

I guess it is hard to do this for older versions of recipes though.
afaik bitbake -b will not build things one depends on and bitbake recipe
will take either the pinned version or otherwise the last one a non-negative
DEFAULT_PREFERENCE.

Frans.

>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  9:07               ` Frans Meulenbroeks
@ 2010-07-30  9:09                 ` Graeme Gregory
  2010-07-30  9:36                 ` Marcin Juszkiewicz
  1 sibling, 0 replies; 23+ messages in thread
From: Graeme Gregory @ 2010-07-30  9:09 UTC (permalink / raw)
  To: openembedded-devel

 On 30/07/10 10:07, Frans Meulenbroeks wrote:
> 2010/7/30 Graeme Gregory <dp@xora.org.uk>
>
>>  On 30/07/10 09:48, Frans Meulenbroeks wrote:
>>> 2010/7/30 Graeme Gregory <dp@xora.org.uk>
>>>
>>>>  On 30/07/10 09:22, Koen Kooi wrote:
>>>>> On 30-07-10 09:21, Esben Haabendal wrote:
>>>>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister
>>>>> <philip@balister.org> wrote:
>>>>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>>>> Hash: SHA1
>>>>>>>>
>>>>>>>> On 29-07-10 10:50, Frans Meulenbroeks wrote:
>>>>>>>>> Dear all,
>>>>>>>>>
>>>>>>>>> Given the discussions on quality that sometimes pop up (and also
>>>>>>>>> triggered
>>>>>>>>> by Robert's message), I decided to kick off a bitbake -k world.
>>>>>>>> Could you first explain to me why 'bitbake world' is a good way to
>>>>>>>> measure quality?
>>>>>>>>
>>>>>>>> I would think that building something like console-image and
>>>>> looking at
>>>>>>>> the following would be a much better metric:
>>>>>>>>
>>>>>>>> * does it build?
>>>>>>>> * are all the rootfs types working?
>>>>>>>> * does the image do what it is supposed to do?
>>>>>>>> * Are all the licenses of the output packages correct?
>>>>>>>> * Do the output packages have any spurious deps?
>>>>>>>> * Is the content of the output packages correct?
>>>>>>>> * Are there any known CVEs in the resulting packages?
>>>>>>>> * Did packaged-staging do its job?
>>>>>>>> * What kind of QA errors and warnings were raised?
>>>>>>>> * Did all recipes pass recipe_sanity?
>>>>>>>> * Did all recipes conform to oe-stylize.py?
>>>>>>>>
>>>>>>>> etc
>>>>>>>>
>>>>>>>> I would actually advocate removing the 'world' feature from
>>>> bitbake/OE
>>>>>>>> to stop people from wasting time on looking at bitbake world and
>> have
>>>>>>>> them fix actual problems.
>>>>>>> bitbake world seems to be the source of pointless listserv
>>>>> discussions. Does
>>>>>>> it serve any purpose?
>>>>>> Pointless or not really depends on how you look at quality.
>>>>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
>>>>>> rather pointless to have bitbake world.
>>>>>> But for those of us who have a different view on what quality is, then
>>>>>> bitbake world serves a purpose.
>>>>> As Thomas points out, as soon as you start blacklisting things (which
>>>>> actually increases quality), bitbake world doesn't work anymore.
>>>>> That alone should be enough to kill it.
>>>> Time to jump in the cage here.
>>>>
>>>> "Quality" is achieved by comparing a set of known specifications against
>>>> a known data set. In the software case this means we need a good set of
>>>> specifications which we are testing against. We also need to know in
>>>> detail what we are testing against this set of specifications.
>>>>
>>>> bitbake world meets neither of these criteria. You have no idea what
>>>> your testing against, you also have no idea what you are submitting for
>>>> test. A random selection of 8500 files in OE. It also doesn't take into
>>>> account known combinations which always fail. Angstrom took care of
>>>> these known failures by creating the concept of a blacklist.
>>>>
>>>> In fact if you tell me bitbake world fails, I would actually suggest
>>>> that is a test pass, it is an expected fail.
>>>>
>>>> Graeme
>>>>
>>>> Actually I expect it to fail, but I am eager to learn which recipes
>> fail.
>>> And yes, it might well be that this is not a good test. If you have
>>> suggestions for a better test that tests all our recipes feel free to
>> speak
>>> up.
>>>
>>> The dependency analysis of bitbake world already showed that there are
>>> several issues (as listed above).
>>> E.g. there are apparently dependencies on non existing recipes.
>>> Instead of shooting the messenger and killing the tool it would be better
>>> to  resolve these (by either fixing them as I have seen JaMa did for some
>>> recipes in the past) or by removing the recipes.
>>> Keeping them around as junk does not improve things.
>>>
>>> And failure of bitbake -k world is not necessarily bad. At least it will
>>> give some insight in the weak spots.
>>>
>> More interesting to me would be an algorithm more like.
>>
>> while recipe in recips/*.bb; do
>>    rm -rf tmp/ ; bitbake recipe
>> done
>>
>> with the test noting if the fail is due to a blacklisted dependency, a
>> totally missing dependency (recipe been deleted sometime in past) or an
>> actual compile fail due to a missing DEPENDS entry somewhere in the tree.
>>
>> But this is going to burn CPU time like never before.
>>
>> Graeme
>>
>>
> Graeme,
>
> Definitely an interesting test. Actually with packaged staging this might
> become manageble.
> I would not mind running such a test, even if it takes a week or so.
>
> I guess it is hard to do this for older versions of recipes though.
> afaik bitbake -b will not build things one depends on and bitbake recipe
> will take either the pinned version or otherwise the last one a non-negative
> DEFAULT_PREFERENCE.
>
> Frans.
>
bitbake blah-x.x.x should work to build exact versions with dependencies
though.

G




^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  9:07               ` Frans Meulenbroeks
  2010-07-30  9:09                 ` Graeme Gregory
@ 2010-07-30  9:36                 ` Marcin Juszkiewicz
  1 sibling, 0 replies; 23+ messages in thread
From: Marcin Juszkiewicz @ 2010-07-30  9:36 UTC (permalink / raw)
  To: openembedded-devel

Dnia piątek, 30 lipca 2010 o 11:07:32 Frans Meulenbroeks napisał(a):
> > More interesting to me would be an algorithm more like.
> > 
> > while recipe in recips/*.bb; do
> >    rm -rf tmp/ ; bitbake recipe
> > done
> > 
> > with the test noting if the fail is due to a blacklisted dependency, a
> > totally missing dependency (recipe been deleted sometime in past) or an
> > actual compile fail due to a missing DEPENDS entry somewhere in the tree.
> > 
> > But this is going to burn CPU time like never before.

> Definitely an interesting test. Actually with packaged staging this might
> become manageble.
> I would not mind running such a test, even if it takes a week or so.

I did such ones for Poky and with packaged staging dir outside of tmpdir it 
works very good. Most of time is spent on removing tmp and repopulating 
it from packages.
 
> I guess it is hard to do this for older versions of recipes though.
> afaik bitbake -b will not build things one depends on and bitbake recipe
> will take either the pinned version or otherwise the last one a
> non-negative DEFAULT_PREFERENCE.

"bitbake recipe-version" works but you will need more work to get 'version' 
part as it can contain SRCREV etc.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz





^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  9:01             ` Frans Meulenbroeks
@ 2010-07-30 15:39               ` Dr. Michael Lauer
  0 siblings, 0 replies; 23+ messages in thread
From: Dr. Michael Lauer @ 2010-07-30 15:39 UTC (permalink / raw)
  To: openembedded-devel

Am 30.07.2010 um 11:01 schrieb Frans Meulenbroeks:
>> people are quite clear on this, pick a version and stick with it.
>> 
> 
> You're hitting the nail on head with this. One of the problems of OE is that
> we want to support too many versions at the same time.
> dev head should not have two versions of bluez in the first place.

With this I wholeheartedly agree (in principle – there will always
be exceptions due to combination problems).

> BTW and blacklisting is only a side observation on why things fail.
> It would still be good to fix the dependency issues.

Agreed.

:M:




^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-30  8:34         ` Frans Meulenbroeks
  2010-07-30  8:41           ` Koen Kooi
@ 2010-07-31 23:12           ` Richard Purdie
  2010-08-01  5:10             ` Frans Meulenbroeks
  2010-08-01 14:05             ` Philip Balister
  1 sibling, 2 replies; 23+ messages in thread
From: Richard Purdie @ 2010-07-31 23:12 UTC (permalink / raw)
  To: openembedded-devel

On Fri, 2010-07-30 at 10:34 +0200, Frans Meulenbroeks wrote:
> 2010/7/30 Koen Kooi <k.kooi@student.utwente.nl>
> > On 30-07-10 09:21, Esben Haabendal wrote:
> > > On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister <philip@balister.org>
> > wrote:
> > >> On 07/29/2010 05:45 AM, Koen Kooi wrote:

> > >>> I would actually advocate removing the 'world' feature from bitbake/OE
> > >>> to stop people from wasting time on looking at bitbake world and have
> > >>> them fix actual problems.
> > >>
> > >> bitbake world seems to be the source of pointless listserv discussions.
> > Does
> > >> it serve any purpose?
> > >
> > > Pointless or not really depends on how you look at quality.
> > >
> > > If you look at it as you, Koen and other OE long-timers, yes, it looks
> > > rather pointless to have bitbake world.
> > > But for those of us who have a different view on what quality is, then
> > > bitbake world serves a purpose.
> >
> > As Thomas points out, as soon as you start blacklisting things (which
> > actually increases quality), bitbake world doesn't work anymore.
> 
> Blacklisting does *NOT* increase quality. It just hides the problem and as
> such it is ostrich behaviour.
> 
> Instead of masking the problem, better fix things. That is what improves
> quality!
> 
> For me a non building recipe is a sign of poor quality.
> 
> BTW: to avoid the blacklisting issue, I've restarted my test with minimal
> distro.
> Results will probably be available after the weekend.

"world" is used by Poky quite successfully. In Poky we expect everything
to build with a known list of things that don't. Our aim is to have that
list consisting of zero items and I intend to see that happens :).

I don't think many people have been watching Poky recently but we've
been quietly having a massive quality control effort on the metadata in
there. This has included:

a) Removal of legacy staging
b) Using BBCLASSEXTEND = native where it makes sense
c) Using nativesdk (no sdk class)
d) Upgrading everything to modern versions of the package concerned
e) Only allowing sane pkgconfig files
f) Enhancing the metadata with licence and other information

Its possible to contemplate this due to Poky's version policy and size
and its still taking significant effort. OE has always been pulled in
many directions and this is both a good and a bad thing. The only ways I
can think of to make a dramatic improvement to OE in this area would be
disliked by some of its users so I don't know what the solution is.

There are other good things happening in Poky as well as the above too
btw :)

Cheers,

Richard







^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-31 23:12           ` Richard Purdie
@ 2010-08-01  5:10             ` Frans Meulenbroeks
  2010-08-01 14:05             ` Philip Balister
  1 sibling, 0 replies; 23+ messages in thread
From: Frans Meulenbroeks @ 2010-08-01  5:10 UTC (permalink / raw)
  To: openembedded-devel

2010/8/1 Richard Purdie <rpurdie@rpsys.net>

>
>
> "world" is used by Poky quite successfully. In Poky we expect everything
> to build with a known list of things that don't. Our aim is to have that
> list consisting of zero items and I intend to see that happens :).
>

I would love the see this happen for OE as well.

>
> I don't think many people have been watching Poky recently but we've
> been quietly having a massive quality control effort on the metadata in
> there. This has included:
>
> a) Removal of legacy staging
> b) Using BBCLASSEXTEND = native where it makes sense
> c) Using nativesdk (no sdk class)
> d) Upgrading everything to modern versions of the package concerned
> e) Only allowing sane pkgconfig files
> f) Enhancing the metadata with licence and other information
>

Cool. I'll peek into it.

>
> Its possible to contemplate this due to Poky's version policy and size
> and its still taking significant effort. OE has always been pulled in
> many directions and this is both a good and a bad thing. The only ways I
> can think of to make a dramatic improvement to OE in this area would be
> disliked by some of its users so I don't know what the solution is.
>

*Any* solution (including the current status) will be disliked by some
users.
We need to set a direction. I hope and suggest the TSC will provide some
guidance here.

We can e.g. keep complaining about legacy staging, but if there is no action
nothing will change.

I'm trying to create awareness and do suggestions on how to resolve things.
Unfortunately these are rejected by some, but at the same time these very
same persons fail to provide an alternative scenario (apart from that
*others* need to work on this.

>
> There are other good things happening in Poky as well as the above too
> btw :)
>

I'll keep an eye on it!

Frans


^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-07-31 23:12           ` Richard Purdie
  2010-08-01  5:10             ` Frans Meulenbroeks
@ 2010-08-01 14:05             ` Philip Balister
  2010-08-01 18:48               ` Richard Purdie
  1 sibling, 1 reply; 23+ messages in thread
From: Philip Balister @ 2010-08-01 14:05 UTC (permalink / raw)
  To: openembedded-devel

On 07/31/2010 07:12 PM, Richard Purdie wrote:
> On Fri, 2010-07-30 at 10:34 +0200, Frans Meulenbroeks wrote:
>> 2010/7/30 Koen Kooi<k.kooi@student.utwente.nl>
>>> On 30-07-10 09:21, Esben Haabendal wrote:
>>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister<philip@balister.org>
>>> wrote:
>>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
>
>>>>>> I would actually advocate removing the 'world' feature from bitbake/OE
>>>>>> to stop people from wasting time on looking at bitbake world and have
>>>>>> them fix actual problems.
>>>>>
>>>>> bitbake world seems to be the source of pointless listserv discussions.
>>> Does
>>>>> it serve any purpose?
>>>>
>>>> Pointless or not really depends on how you look at quality.
>>>>
>>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
>>>> rather pointless to have bitbake world.
>>>> But for those of us who have a different view on what quality is, then
>>>> bitbake world serves a purpose.
>>>
>>> As Thomas points out, as soon as you start blacklisting things (which
>>> actually increases quality), bitbake world doesn't work anymore.
>>
>> Blacklisting does *NOT* increase quality. It just hides the problem and as
>> such it is ostrich behaviour.
>>
>> Instead of masking the problem, better fix things. That is what improves
>> quality!
>>
>> For me a non building recipe is a sign of poor quality.
>>
>> BTW: to avoid the blacklisting issue, I've restarted my test with minimal
>> distro.
>> Results will probably be available after the weekend.
>
> "world" is used by Poky quite successfully. In Poky we expect everything
> to build with a known list of things that don't. Our aim is to have that
> list consisting of zero items and I intend to see that happens :).

But Poky operates under different conditions than the main OE meta-data. 
Since you more focus on what Poky builds, you do not need to support the 
variety of recipes in the OE meta-data.

Philip


>
> I don't think many people have been watching Poky recently but we've
> been quietly having a massive quality control effort on the metadata in
> there. This has included:
>
> a) Removal of legacy staging
> b) Using BBCLASSEXTEND = native where it makes sense
> c) Using nativesdk (no sdk class)
> d) Upgrading everything to modern versions of the package concerned
> e) Only allowing sane pkgconfig files
> f) Enhancing the metadata with licence and other information
>
> Its possible to contemplate this due to Poky's version policy and size
> and its still taking significant effort. OE has always been pulled in
> many directions and this is both a good and a bad thing. The only ways I
> can think of to make a dramatic improvement to OE in this area would be
> disliked by some of its users so I don't know what the solution is.
>
> There are other good things happening in Poky as well as the above too
> btw :)
>
> Cheers,
>
> Richard
>
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



^ permalink raw reply	[flat|nested] 23+ messages in thread
* Re: OE recipe tree quality
  2010-08-01 14:05             ` Philip Balister
@ 2010-08-01 18:48               ` Richard Purdie
  0 siblings, 0 replies; 23+ messages in thread
From: Richard Purdie @ 2010-08-01 18:48 UTC (permalink / raw)
  To: openembedded-devel

On Sun, 2010-08-01 at 10:05 -0400, Philip Balister wrote:
> On 07/31/2010 07:12 PM, Richard Purdie wrote:
> > On Fri, 2010-07-30 at 10:34 +0200, Frans Meulenbroeks wrote:
> >> 2010/7/30 Koen Kooi<k.kooi@student.utwente.nl>
> >>> On 30-07-10 09:21, Esben Haabendal wrote:
> >>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister<philip@balister.org>
> >>> wrote:
> >>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> >
> >>>>>> I would actually advocate removing the 'world' feature from bitbake/OE
> >>>>>> to stop people from wasting time on looking at bitbake world and have
> >>>>>> them fix actual problems.
> >>>>>
> >>>>> bitbake world seems to be the source of pointless listserv discussions.
> >>> Does
> >>>>> it serve any purpose?
> >>>>
> >>>> Pointless or not really depends on how you look at quality.
> >>>>
> >>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
> >>>> rather pointless to have bitbake world.
> >>>> But for those of us who have a different view on what quality is, then
> >>>> bitbake world serves a purpose.
> >>>
> >>> As Thomas points out, as soon as you start blacklisting things (which
> >>> actually increases quality), bitbake world doesn't work anymore.
> >>
> >> Blacklisting does *NOT* increase quality. It just hides the problem and as
> >> such it is ostrich behaviour.
> >>
> >> Instead of masking the problem, better fix things. That is what improves
> >> quality!
> >>
> >> For me a non building recipe is a sign of poor quality.
> >>
> >> BTW: to avoid the blacklisting issue, I've restarted my test with minimal
> >> distro.
> >> Results will probably be available after the weekend.
> >
> > "world" is used by Poky quite successfully. In Poky we expect everything
> > to build with a known list of things that don't. Our aim is to have that
> > list consisting of zero items and I intend to see that happens :).
> 
> But Poky operates under different conditions than the main OE meta-data. 
> Since you more focus on what Poky builds, you do not need to support the 
> variety of recipes in the OE meta-data.

Totally. I was mainly responding to the "world is useless, we should
remove it" comment and also showing that blacklists are used by others
too, in general with success.

Cheers,

Richard






^ permalink raw reply	[flat|nested] 23+ messages in thread
end of thread, other threads:[~2010-08-01 18:49 UTC | newest]

Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-29  8:50 OE recipe tree quality Frans Meulenbroeks
2010-07-29  9:42 ` Thomas Zimmermann
2010-07-29  9:45 ` Koen Kooi
2010-07-29 10:32   ` Frans Meulenbroeks
2010-07-29 12:07   ` Philip Balister
2010-07-29 12:15     ` Frans Meulenbroeks
2010-07-30  7:21     ` Esben Haabendal
2010-07-30  8:22       ` Koen Kooi
2010-07-30  8:31         ` Graeme Gregory
2010-07-30  8:48           ` Frans Meulenbroeks
2010-07-30  8:56             ` Graeme Gregory
2010-07-30  9:07               ` Frans Meulenbroeks
2010-07-30  9:09                 ` Graeme Gregory
2010-07-30  9:36                 ` Marcin Juszkiewicz
2010-07-30  8:54           ` Esben Haabendal
2010-07-30  8:34         ` Frans Meulenbroeks
2010-07-30  8:41           ` Koen Kooi
2010-07-30  9:01             ` Frans Meulenbroeks
2010-07-30 15:39               ` Dr. Michael Lauer
2010-07-31 23:12           ` Richard Purdie
2010-08-01  5:10             ` Frans Meulenbroeks
2010-08-01 14:05             ` Philip Balister
2010-08-01 18:48               ` Richard Purdie

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.