Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] opensp and openssh recipe upgrades
Date: Mon,  7 May 2012 15:49:12 -0700	[thread overview]
Message-ID: <cover.1336430865.git.scott.a.garman@intel.com> (raw)

Hello,

This pull request includes upgrades for the opensp and openssh recipes.
They have been build-tested on all 5 of our QEMU architectures. The
distro tracking updates include a couple of recipes that I missed in
previous pull requests.

Scott

The following changes since commit 2929e7d590862d9649458c90804e79a1dce40423:

  glib-2.0: Fix issues with libelf dependency creeping in (2012-05-07 10:53:24 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib sgarman/recipe-upgrades-oe
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades-oe

Scott Garman (3):
  openssh: upgrade to 6.0p1
  opensp: upgrade to 1.5.2
  distro_tracking: updates for upgraded recipes

 .../conf/distro/include/distro_tracking_fields.inc |   25 +-
 .../openssh/{openssh-5.9p1 => openssh-6.0p1}/init  |    0
 .../{openssh-5.9p1 => openssh-6.0p1}/nostrip.patch |    0
 .../{openssh-5.9p1 => openssh-6.0p1}/ssh_config    |    0
 .../openssh/{openssh-5.9p1 => openssh-6.0p1}/sshd  |    0
 .../{openssh-5.9p1 => openssh-6.0p1}/sshd_config   |    0
 .../openssh/{openssh_5.9p1.bb => openssh_6.0p1.bb} |    8 +-
 .../opensp/opensp/attributevalue.patch             |   65 -
 .../opensp/opensp/fix-docdir.patch                 |   17 -
 meta/recipes-devtools/opensp/opensp/m4.patch       | 1928 --------------------
 .../opensp/opensp/rangmap-fix.patch                |   18 -
 .../opensp/{opensp_1.5.bb => opensp_1.5.2.bb}      |   20 +-
 12 files changed, 23 insertions(+), 2058 deletions(-)
 rename meta/recipes-connectivity/openssh/{openssh-5.9p1 => openssh-6.0p1}/init (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.9p1 => openssh-6.0p1}/nostrip.patch (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.9p1 => openssh-6.0p1}/ssh_config (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.9p1 => openssh-6.0p1}/sshd (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.9p1 => openssh-6.0p1}/sshd_config (100%)
 rename meta/recipes-connectivity/openssh/{openssh_5.9p1.bb => openssh_6.0p1.bb} (94%)
 delete mode 100644 meta/recipes-devtools/opensp/opensp/attributevalue.patch
 delete mode 100644 meta/recipes-devtools/opensp/opensp/fix-docdir.patch
 delete mode 100644 meta/recipes-devtools/opensp/opensp/m4.patch
 delete mode 100644 meta/recipes-devtools/opensp/opensp/rangmap-fix.patch
 rename meta/recipes-devtools/opensp/{opensp_1.5.bb => opensp_1.5.2.bb} (71%)

-- 
1.7.5.4




             reply	other threads:[~2012-05-07 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 22:49 Scott Garman [this message]
2012-05-07 22:49 ` [PATCH 1/3] openssh: upgrade to 6.0p1 Scott Garman
2012-05-07 22:49 ` [PATCH 2/3] opensp: upgrade to 1.5.2 Scott Garman
2012-05-07 22:49 ` [PATCH 3/3] distro_tracking: updates for upgraded recipes Scott Garman
2012-05-08 15:20 ` [PATCH 0/3] opensp and openssh recipe upgrades Richard Purdie

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.1336430865.git.scott.a.garman@intel.com \
    --to=scott.a.garman@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