All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Kramer <robk@starhub.net.sg>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake-1.6 crashes on 'which'.
Date: Mon, 23 Oct 2006 10:07:49 +0800	[thread overview]
Message-ID: <ehh80o$7dl$1@sea.gmane.org> (raw)
In-Reply-To: 1161538860.5545.7.camel@localhost.localdomain

Richard Purdie wrote:
> I can't seem to reproduce that. Can you give a sequence of commands
> which result in the failure?

Hmm, it seems to happen rare enough not to be a problem. I was trying to get
a new version of a package visible to a running bitbake by doing reparses,
but I think that doesn't work (i.e, it doesn't want to switch to the newest
version). After it crashed out and was restarted, it selected my new
version properly.

Cheers,

    Rob




  parent reply	other threads:[~2006-10-23  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  7:02 Bitbake-1.6 crashes on 'which' Rob Kramer
2006-10-18  7:19 ` Rob Kramer
2006-10-21 12:10   ` Richard Purdie
2006-10-22  2:57     ` Rob Kramer
2006-10-22 17:41       ` Richard Purdie
2006-10-22 18:32         ` Michael 'Mickey' Lauer
2006-10-23  2:07         ` Rob Kramer [this message]
2006-10-18  8:04 ` Holger Freyther

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='ehh80o$7dl$1@sea.gmane.org' \
    --to=robk@starhub.net.sg \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.