All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Spinler <mspinler@linux.vnet.ibm.com>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Recipe Renames, etc
Date: Wed, 10 Oct 2018 13:40:18 -0500	[thread overview]
Message-ID: <9dc677b3c95c2bc7e7c5a11a97df49a7@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAO=notyKtrecZeAypPcjY7qi6rBqj_cPwPosFRds=wYpeHW8wA@mail.gmail.com>

On 2018-10-02 10:28, Patrick Venture wrote:
> I've sent a bunch of recipe renames, but I'm still updating each with
> an individual tested footer.  I will try marking them all as WIP now
> 
> Patrick


Hi Patrick,

I think you broke master with these.  For example, the phosphor-rest 
recipe - it
has a default url-config.json, and then a layer specific file gets 
applied from
the meta-ibm layer, like:

meta-ibm/recipes-phosphor/interfaces/phosphor-rest/url_config.json

However, from the log.do_unpack from the phosphor-rest build, it doesn't 
look there,
it now only looks in phosphor-rest%.  So any override directory without 
a % isn't
being found.

I haven't looked to see what all is broken yet and in how many layers, 
at least
our phosphor-rest and phosphor-gevent, which is why the web UI stopped 
working
on witherspoon.  Not sure if any other systems are also having problems.

  reply	other threads:[~2018-10-10 18:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 15:28 Recipe Renames, etc Patrick Venture
2018-10-10 18:40 ` Matt Spinler [this message]
2018-10-10 18:45   ` Patrick Venture
2018-10-10 18:46     ` Patrick Venture
2018-10-10 18:50       ` Patrick Venture
2018-10-10 19:00         ` Patrick Venture
2018-10-10 19:01         ` Matt Spinler
2018-10-10 19:01           ` Patrick Venture
2018-10-10 19:02             ` Patrick Venture
2018-10-10 19:19               ` Matt Spinler
2018-10-10 19:20                 ` Patrick Venture

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=9dc677b3c95c2bc7e7c5a11a97df49a7@linux.vnet.ibm.com \
    --to=mspinler@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.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 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.