Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Denys Dmytriyenko <denys@ti.com>,
	Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot: update to 2015.01
Date: Thu, 22 Jan 2015 10:17:42 -0500	[thread overview]
Message-ID: <20150122151742.GP20639@denix.org> (raw)
In-Reply-To: <CAJTo0LbgjEA63TCrh=bE7HuLWE=vi5PTgK1h0f0-YLBaXgbjnA@mail.gmail.com>

On Thu, Jan 22, 2015 at 03:02:06PM +0000, Burton, Ross wrote:
> On 22 January 2015 at 14:57, Denys Dmytriyenko <denis@denix.org> wrote:
> 
> > Please note that he's talking about current 2014.07 version, not the
> > update!
> > Can you confirm that it works or fails on the autobuilder?
> >
> 
> Sorry, got lost in the thread.  The old version works fine, the upgrade
> breaks.

That's not the case for the rest of us, unfortunately...

I'm suspecting sstate got something to do with the fact that it still works 
for the old version on autobuilder.


Let me emphasise it - this specific u-boot-fw-utils-cross recipe used to 
build fine, but now fails in the same exact way regardless of the version, 
either current 2014.07 or the updated 2015.01.

So, it seems to me that fixing it is rather out of scope of this version 
update patch... :)

I'm thinking of 2 short-term workarounds - don't update this particular recipe 
to the new version; or remove it altogether. I'm sure Otavio wouldn't be happy 
either way, but fixing it should probably be a separate effort...

-- 
Denys


  parent reply	other threads:[~2015-01-22 15:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 16:09 [PATCH] u-boot: update to 2015.01 Denys Dmytriyenko
2015-01-20 20:19 ` Denys Dmytriyenko
2015-01-21 13:17 ` Otavio Salvador
2015-01-21 19:11   ` Denys Dmytriyenko
2015-01-21 20:11     ` Otavio Salvador
2015-01-21 20:20       ` Denys Dmytriyenko
2015-01-22  9:50         ` Raphael Philipe
2015-01-22 12:05           ` Burton, Ross
2015-01-22 14:57             ` Denys Dmytriyenko
2015-01-22 15:02               ` Burton, Ross
2015-01-22 15:12                 ` Raphael Philipe
2015-01-22 15:17                 ` Denys Dmytriyenko [this message]
2015-01-22 15:40                   ` Otavio Salvador
2015-01-22 16:00                     ` Denys Dmytriyenko
2015-01-22 16:05                       ` Otavio Salvador
2015-01-22 21:23           ` Denys Dmytriyenko
2015-01-23  3:50             ` Denys Dmytriyenko
2015-01-22 16:07         ` Denys Dmytriyenko
2015-01-22 16:12           ` Otavio Salvador
2015-01-22 16:33             ` Denys Dmytriyenko
2015-01-21 20:25       ` Raphael Philipe
2015-01-21 20:28         ` Denys Dmytriyenko
2015-01-21 20:31           ` Raphael Philipe
2015-01-21 20:35             ` Denys Dmytriyenko
2015-01-21 20:48               ` Raphael Philipe

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=20150122151742.GP20639@denix.org \
    --to=denis@denix.org \
    --cc=denys@ti.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=ross.burton@intel.com \
    /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