Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: bitbake -s broken?
Date: Thu, 09 Jun 2011 08:26:27 -0700	[thread overview]
Message-ID: <4DF0E623.9080603@intel.com> (raw)
In-Reply-To: <15E9EFF9-235F-45CF-A2AC-BFE047710335@dominion.thruhere.net>

On 06/08/2011 03:20 AM, Koen Kooi wrote:
> Hi,
>
> Apart from -b being broken as I reported earlier -s seems to be broken as well now:
>
> koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-gnome$ MACHINE=beagleboard bitbake -s  | head -n10
> Loading cache...done.
> Loaded 1622 entries from dependency cache.
> WARNING: No bb files matched BBFILE_PATTERN_htc-layer '^/OE/tentacle/sources/meta-smartphone/meta-htc/'
> Package Name                                   Latest Version         Preferred Version
> ============                                   ==============         =================
>
> <bb.cache.CoreRecipeInfo object at 0x3c96750>                    :171-r3
> <bb.cache.CoreRecipeInfo object at 0x3c96710>                  :2.8.0-r1
> <bb.cache.CoreRecipeInfo object at 0x3c96750>              :1.0.0c-r13.0
> <bb.cache.CoreRecipeInfo object at 0x3c96710>                 1:1.0.4-r2

I bisected this error this morning to this commit:

cache.py: Refactory Current Cache implementation
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=8df355140c5afb683cb97fed82f679366e60320b

This bug is preventing me from doing another documentation build audit 
with the latest master.

I have filed bug #1149 to track this issue.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center



      reply	other threads:[~2011-06-09 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 10:20 bitbake -s broken? Koen Kooi
2011-06-09 15:26 ` Scott Garman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DF0E623.9080603@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox