From: Patrick Ohly <patrick.ohly@intel.com>
To: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sanity.bbclass: fix AttributeError in mirror format checks
Date: Mon, 03 Jul 2017 11:56:39 +0200 [thread overview]
Message-ID: <1499075799.5259.77.camel@intel.com> (raw)
In-Reply-To: <20170630112411.11705-1-mikko.ylinen@linux.intel.com>
On Fri, 2017-06-30 at 14:24 +0300, Mikko Ylinen wrote:
> mirrors is a list after split() and results in:
>
> AttributeError: 'list' object has no attribute 'strip'
>
> when the 'mirror values are pairs' check fails.
>
> Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
> ---
> meta/classes/sanity.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index e8064ac483..1f74026e13 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -839,7 +839,7 @@ def check_sanity_everybuild(status, d):
>
> # Split into pairs
> if len(mirrors) % 2 != 0:
> - bb.warn('Invalid mirror variable value for %s: %s, should contain paired members.' % (mirror_var, mirrors.strip()))
> + bb.warn('Invalid mirror variable value for %s: %s, should contain paired members.' % (mirror_var, str(mirrors).strip()))
.strip() is redundant here, because str(mirrors) will produce [...],
i.e. the string will never have leading or trailing spaces.
--
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.
prev parent reply other threads:[~2017-07-03 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 11:24 [PATCH] sanity.bbclass: fix AttributeError in mirror format checks Mikko Ylinen
2017-07-03 9:56 ` Patrick Ohly [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=1499075799.5259.77.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=mikko.ylinen@linux.intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox