Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [v2 PATCH] kernel.bbclass, image.bbclass: Implement kernel INITRAMFS dependency and bundling
Date: Fri, 27 Sep 2013 11:33:26 -0500	[thread overview]
Message-ID: <5245B356.7030703@windriver.com> (raw)
In-Reply-To: <1380272728.18603.414.camel@ted>

On 09/27/2013 04:05 AM, Richard Purdie wrote:
> On Fri, 2013-09-27 at 10:07 +0200, Andrea Adami wrote:
>> On Sat, Aug 24, 2013 at 7:15 PM, Richard Purdie
>> <richard.purdie@linuxfoundation.org> wrote:
>> With 1.5 approaching I'd like to have the issue solved as soon as possible.
>> Richard, when is deadline for core-patches?
> 
> Basically ASAP. The next release build is the start of next week but any
> patches going into that need to have been run through an autobuilder
> cycle first.
> 
> This is the first I've heard of the problem, other than some comments
> about possible problems on irc. Can someone please open up a bug for
> this and clearly describe what used to work and now doesn't and what the
> possible fixes or workarounds are?
> 
> I don't think anyone likes regressions however if we don't have the open
> bug, its very hard to track.
> 
> You say you've talked to Bruce/Jason but why didn't the discussion
> happen on the mailing list? That way others may have been able to help
> and now I could read back the list and see for myself what the issue is.
> As it is, I simply don't know other than the need to set a new variable
> which is hinted at above...
> 


What was needed most was a defect detailing the configuration setup.  The reason I have not hit this problem nor any of the other autobuilders was that it required a very specific way to setup the recipes to depend on each other, but not circularly.

Andrea sent full details to Bruce, who sent them to me and I built it this morning.  It took very little time to isolate the problem but it was one of those oh so subtle issues (patch is sent to oe-core).  Perhaps in the future we can just get a Bugzilla opened right away.  I don't like regressions either. :-)

Andrea replied to me in IRC, "I'll test the new patch soon". 

Cheers,
Jason.



      parent reply	other threads:[~2013-09-27 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 23:04 [v2 PATCH] kernel.bbclass, image.bbclass: Implement kernel INITRAMFS dependency and bundling Jason Wessel
2013-08-23  6:16 ` Khem Raj
2013-08-23 12:56   ` Jason Wessel
2013-08-26  8:33     ` Andrea Adami
2013-08-24 17:15 ` Richard Purdie
2013-09-27  8:07   ` Andrea Adami
2013-09-27  9:05     ` Richard Purdie
2013-09-27 11:59       ` Andrea Adami
2013-09-27 12:33         ` Bruce Ashfield
2013-09-27 16:33       ` Jason Wessel [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=5245B356.7030703@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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