All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Conroy <Chris.Conroy@hillcrestlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-toolchain continues to woe
Date: Fri, 13 Nov 2009 10:58:34 -0500	[thread overview]
Message-ID: <1258127914.4913.26.camel@conroy-linux> (raw)
In-Reply-To: <200911130219.56218.holger+oe@freyther.de>

On Fri, 2009-11-13 at 02:19 +0100, Holger Hans Peter Freyther wrote:
> On Thursday 12 November 2009 16:29:36 Chris Conroy wrote:
> > > I submitted a patch to opkg back in September to fix this error message
> > > to be a bit more useful. If you upgrade to opkg >=216 it will save you
> > > some headaches whenever this error occurs.
> > 
> > Apologies. I should have read your error message more closely since it
> > looks like you are getting the extra debug information from my patch.
> > Feel free to make a patch with more debug info for said error or just
> > let me know what you think would be appropriate and I can submit a new
> 
> 
> Hi,
> 
> Koen recently upgraded opkg* to something above >= 216.
> 
> regards
> 	holger

Hence my second message where I realized that and apologized for my
idiocy :P

--Chris



      reply	other threads:[~2009-11-13 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  3:57 meta-toolchain continues to woe Holger Hans Peter Freyther
2009-11-12  4:34 ` Graham Gower
2009-11-12  4:49   ` Holger Hans Peter Freyther
2009-11-12  5:11     ` Holger Hans Peter Freyther
2009-11-12 12:09       ` Richard Purdie
2009-11-12 12:28         ` Holger Hans Peter Freyther
2009-11-12 15:14   ` Chris Conroy
2009-11-12 15:29     ` Chris Conroy
2009-11-12 21:16       ` Graham Gower
2009-11-13 19:48         ` Khem Raj
2009-11-13  1:19       ` Holger Hans Peter Freyther
2009-11-13 15:58         ` Chris Conroy [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=1258127914.4913.26.camel@conroy-linux \
    --to=chris.conroy@hillcrestlabs.com \
    --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.