From: Richard Purdie <rpurdie@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: poky@yoctoproject.org
Subject: Re: bitbake package-index broken?
Date: Sun, 28 Nov 2010 16:19:17 +0000 [thread overview]
Message-ID: <1290961157.27143.348.camel@rex> (raw)
In-Reply-To: <4CED06A9.8060806@mlbassoc.com>
On Wed, 2010-11-24 at 05:35 -0700, Gary Thomas wrote:
> On 11/24/2010 04:47 AM, Joshua Lock wrote:
> > On Wed, 2010-11-24 at 04:33 -0700, Gary Thomas wrote:
> >> On 11/24/2010 03:56 AM, Gary Thomas wrote:
> >>> With a recent build, bitbake package-index doesn't seem to do anything.
> >>> e.g. if I look at tmp/deploy/ipk/*/Packages.gz before and after, there
> >>> are no changes.
> >>>
> >>> I tried to build a simple package and add it to my database. Sadly,
> >>> it's not being updated at all, so the new package does not appear on
> >>> the board.
> >>>
> >>> Any ideas what might be wrong?
> >>
> >> A quick check shows that do_build() in the package-index recipe is never
> >> really run!
> >>
> >> I found a workaround by just building an image which has a root file system.
> >> This also forces a package database rebuild. It would be nice to figure out
> >> what's broken though (it certainly _used_ to work)
> >>
> >
> > I'm not really familiar with the ipk classes so can't offer a quick
> > solution, could I ask you to file a bug so that we can track this issue
> > and assign resources to fix?
>
> Done - bug #544
I've a fix I'll push shortly. The reason was that we marked do_build as
noexec and package-index did all its work in do_build. The updates
changes this and marks more tasks in that recipe as noexec to make
things more efficient.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-28 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 10:56 bitbake package-index broken? Gary Thomas
2010-11-24 11:33 ` Gary Thomas
2010-11-24 11:47 ` Joshua Lock
2010-11-24 12:35 ` Gary Thomas
2010-11-28 16:19 ` Richard Purdie [this message]
2011-11-30 13:27 ` Robert Berger
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=1290961157.27143.348.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=poky@yoctoproject.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.