Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [jethro][PATCH 00/20] Backports from master (cover letter only)
Date: Fri, 11 Dec 2015 16:44:26 +1300	[thread overview]
Message-ID: <cover.1449805448.git.paul.eggleton@linux.intel.com> (raw)

Backports to jethro, mostly of fixes relating to the SDK and extensible
SDK.


The following changes since commit 224bcc2ead676600bcd9e290ed23d9b2ed2f481e:

  rpcbind: Security Advisory - rpcbind - CVE-2015-7236 (2015-12-08 00:18:12 -0800)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/jethro-fixes-oecore
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/jethro-fixes-oecore

Fang Jia (1):
  toolchain-scripts.bbclass: unset command_not_found_handle

Jean-Francois Dagenais (1):
  toolchain-shar-relocate: don't assume last state of env_setup_script
    is good

Mark Hatle (1):
  populate_sdk_ext.bbclass: Be more permissive on the name of the
    buildtools

Paul Eggleton (16):
  classes/distrodata: split SRC_URI properly before determining type
  oeqa/selftest/devtool: fix test if build directory is not inside
    COREBASE
  oeqa/selftest/layerappend: fix test if build directory is not inside
    COREBASE
  classes/metadata_scm: fix git errors showing up on non-git
    repositories
  classes/license: fix intermittent license collection warning
  classes/populate_sdk_ext: tidy up preparation log file writing
  classes/populate_sdk_ext: make it clear when SDK installation has
    failed
  classes/populate_sdk_ext: tweak reporting of workspace exclusion
  classes/populate_sdk_ext: fail if SDK_ARCH != BUILD_ARCH
  toolchain-shar-extract.sh: proper fix for additional env setup scripts
  scripts/gen-lockedsig-cache: improve output
  toolchain-shar-extract.sh: do not allow $ in paths for ext SDK
  devtool: upgrade: fix removing other recipes from workspace on reset
  devtool: upgrade: fix updating PV and SRCREV
  devtool: upgrade: remove erroneous error when not renaming recipe
  devtool: upgrade: fetch remote repository before checking out new
    revision

Tzu-Jung Lee (1):
  devtool: include do_patch in SRCTREECOVEREDTASKS

 meta/classes/distrodata.bbclass        |  4 ++--
 meta/classes/license.bbclass           |  1 +
 meta/classes/metadata_scm.bbclass      | 20 +++++++++----------
 meta/classes/populate_sdk_ext.bbclass  | 15 ++++++++------
 meta/classes/toolchain-scripts.bbclass |  1 +
 meta/files/toolchain-shar-extract.sh   | 15 ++++++++++++--
 meta/lib/oe/copy_buildsystem.py        |  5 +++--
 meta/lib/oeqa/selftest/devtool.py      |  2 +-
 meta/lib/oeqa/selftest/layerappend.py  |  9 ++++++---
 scripts/gen-lockedsig-cache            | 13 +++++++++---
 scripts/lib/devtool/standard.py        |  4 ++--
 scripts/lib/devtool/upgrade.py         | 36 ++++++++++++++++++++--------------
 12 files changed, 79 insertions(+), 46 deletions(-)

-- 
2.5.0



                 reply	other threads:[~2015-12-11  3:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.1449805448.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@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