From: leonardo.sandoval.gonzalez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/2] Check invalid characters on some recipe metadata
Date: Mon, 17 Aug 2015 07:10:11 +0000 [thread overview]
Message-ID: <cover.1439794714.git.leonardo.sandoval.gonzalez@linux.intel.com> (raw)
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
* insane.bbclass: QA check for invalid chars
* package_deb.bbclass: Opens the control file allowing UTF-8 chars
and handles a string decoding exception, reported on [1]
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6693
The following changes since commit a533776d6ff83b6e3e830137455b8382d002768b:
perf: fix build breakage on kernels after 4.1 (2015-08-12 11:31:49 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lsandov1/package_deb-handle-non-ascii-6693-v2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lsandov1/package_deb-handle-non-ascii-6693-v2
Leonardo Sandoval (2):
insane.bbclass: Check invalid characters (non UTF8) on recipe metadata
package_deb.bbclass: Allow UTF-8 characters on control files
meta/classes/insane.bbclass | 24 +++++++++++++++++++++++-
meta/classes/package_deb.bbclass | 18 +++++++++++-------
2 files changed, 34 insertions(+), 8 deletions(-)
--
1.8.4.5
next reply other threads:[~2015-08-17 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 7:10 leonardo.sandoval.gonzalez [this message]
2015-08-17 7:10 ` [PATCH v2 1/2] insane.bbclass: Check for invalid characters (non UTF8) on recipe metadata leonardo.sandoval.gonzalez
2015-08-17 22:57 ` Christopher Larson
2015-08-25 14:27 ` Leonardo Sandoval
2015-08-26 16:13 ` Leonardo Sandoval
2015-08-26 16:15 ` Christopher Larson
2015-08-17 7:10 ` [PATCH v2 2/2] package_deb.bbclass: Allow UTF-8 characters on control files leonardo.sandoval.gonzalez
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=cover.1439794714.git.leonardo.sandoval.gonzalez@linux.intel.com \
--to=leonardo.sandoval.gonzalez@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