From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@lists.openembedded.org
Subject: preferred version not available
Date: Mon, 18 Jul 2011 21:16:24 +0200 [thread overview]
Message-ID: <4E248688.1030902@vollmann.ch> (raw)
Hello,
this one really drives me crazy.
Here's what I do:
$ bitbake -D -D -D -D -g linux-taurus | fgrep linux-taurus
DEBUG: Cache: /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb
is not cached
DEBUG: BB /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb:
handle(data)
DEBUG: LOAD /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb
DEBUG: CONF /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb:5:
including recipes/linux/ccp-linux.inc
DEBUG: providers for linux-taurus are: ['linux-taurus']
NOTE: preferred version githead of linux-taurus not available (for item
linux-taurus)
It already starts with the first 'DEBUG' line: Why is it not cached.
I have some other recipes for linux-taurus with version numbers that
don't get parsed again because they are cached.
But I can live with that.
What really drives me nuts is the last line: it clearly parsed
linux-taurus_githead.bb before, doesn't give me any error on it,
but then tells me 'preferred version githead of linux-taurus not
available'. It's clearly there, so why is it not available?
The interesting thing is that I don't have any problems with my
other *_githead.bb recipes, only with the linux kernel...
I'd really appreciate any help!
Detlef
next reply other threads:[~2011-07-19 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 19:16 Detlef Vollmann [this message]
2011-07-18 21:02 ` preferred version not available Detlef Vollmann
2011-07-18 21:05 ` Chris Larson
2011-07-19 7:20 ` Detlef Vollmann
2011-07-19 9:53 ` Paul Eggleton
2011-07-19 10:16 ` Detlef Vollmann
2011-07-19 11:25 ` [oe] " Detlef Vollmann
2011-07-19 15:06 ` Chris Larson
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=4E248688.1030902@vollmann.ch \
--to=dv@vollmann.ch \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.