From: Patrick Ohly <patrick.ohly@intel.com>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation
Date: Mon, 08 May 2017 15:36:15 +0200 [thread overview]
Message-ID: <1494250575.4241.328.camel@intel.com> (raw)
In-Reply-To: <1487625169-22282-1-git-send-email-anibal.limon@linux.intel.com>
On Mon, 2017-02-20 at 15:12 -0600, Aníbal Limón wrote:
> + try:
> + ldata = bb.parse.handle(lconf, ldata, include=True)
> + except BaseException as exc:
> + raise LayerError(exc)
Anibal, where is this LayerError class in compatlayer/__init__.py
supposed to come from? It doesn't get imported, leading to:
File
"/fast/work/intel-iot-refkit/openembedded-core/scripts/lib/compatlayer/__init__.py", line 45, in _get_layer_collections
raise LayerError(exc)
NameError: name 'LayerError' is not defined
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-05-08 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 21:12 [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation Aníbal Limón
2017-02-28 20:09 ` Patrick Ohly
2017-02-28 20:33 ` Aníbal Limón
2017-02-28 22:17 ` Patrick Ohly
2017-03-01 4:00 ` Richard Purdie
2017-03-01 7:10 ` Patrick Ohly
2017-03-01 15:12 ` Richard Purdie
2017-03-01 15:51 ` Patrick Ohly
2017-03-01 16:01 ` Richard Purdie
2017-03-01 16:47 ` Patrick Ohly
2017-05-08 13:36 ` Patrick Ohly [this message]
2017-05-08 15:14 ` Aníbal Limón
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=1494250575.4241.328.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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