From: "yaoxp" <yaoxp@cn.fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] insane.bbclass:WARNING: QA Issue: xxx doesn't match the [a-z0-9.+-]+ regex
Date: Wed, 21 Aug 2013 14:28:59 +0800 [thread overview]
Message-ID: <020301ce9e37$b92b36d0$2b81a470$@cn.fujitsu.com> (raw)
Will offer the following warning when there are upper case letters in the BB file name:
WARNING: QA Issue: xxx doesn't match the [a-z0-9.+-]+ regex
Is there such a regulation in yocto that there can't be upper case letters in the BB file name ?
Signed-off-by: Yao Xinpan <yaoxp@cn.fujitsu.com>
---
meta/classes/insane.bbclass | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass index 336beaa..4042e1e 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -776,8 +776,8 @@ python do_package_qa () {
testmatrix = d.getVarFlags("QAPATHTEST")
import re
- # The package name matches the [a-z0-9.+-]+ regular expression
- pkgname_pattern = re.compile("^[a-z0-9.+-]+$")
+ # The package name matches the [A-Za-z0-9.+-]+ regular expression
+ pkgname_pattern = re.compile("^[A-Za-z0-9.+-]+$")
g = globals()
walk_sane = True
@@ -804,7 +804,7 @@ python do_package_qa () {
# Check package name
if not pkgname_pattern.match(package):
package_qa_handle_error("pkgname",
- "%s doesn't match the [a-z0-9.+-]+ regex\n" % package, d)
+ "%s doesn't match the [A-Za-z0-9.+-]+ regex\n" %
+ package, d)
path = "%s/%s" % (pkgdest, package)
if not package_qa_walk(path, warnchecks, errorchecks, skip, package, d):
--
1.7.1
next reply other threads:[~2013-08-21 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 6:28 yaoxp [this message]
2013-08-28 23:18 ` [PATCH] insane.bbclass:WARNING: QA Issue: xxx doesn't match the [a-z0-9.+-]+ regex Andrei Gherzan
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='020301ce9e37$b92b36d0$2b81a470$@cn.fujitsu.com' \
--to=yaoxp@cn.fujitsu.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