Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Scott Garman <scott.a.garman@intel.com>
Subject: [PATCH 0/4] Recipe upgrades: openssh, grep, tar
Date: Sun,  5 Jun 2011 21:49:29 -0700	[thread overview]
Message-ID: <cover.1307331820.git.scott.a.garman@intel.com> (raw)

Good day,

Here are some straightforward recipe upgrades for openssh, grep,
and tar.

Build tested on all five qemu MACHINEs we support. Runtime tested on
qemuarm.

The following changes since commit 6b5d323b6c8960a0999dbafa0422fe127fd0fa97:

  event: don't catch systemexit from handler execution (2011-06-02 23:58:05 +0100)

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

Scott Garman (4):
  openssh: upgrade to v5.8p2
  grep: upgrade to v2.8
  tar: upgrade to v1.26
  distro-tracking: update openssh, tar, and grep

 .../conf/distro/include/distro_tracking_fields.inc |   26 ++++++++++----------
 .../openssh/{openssh-5.6p1 => openssh-5.8p2}/init  |    0
 .../{openssh-5.6p1 => openssh-5.8p2}/nostrip.patch |    0
 .../{openssh-5.6p1 => openssh-5.8p2}/ssh_config    |    0
 .../{openssh-5.6p1 => openssh-5.8p2}/sshd_config   |    0
 .../openssh/{openssh_5.6p1.bb => openssh_5.8p2.bb} |    9 ++++---
 .../grep/{grep_2.7.bb => grep_2.8.bb}              |    7 +++--
 ...tive_1.25.bb => tar-replacement-native_1.26.bb} |    0
 meta/recipes-extended/tar/tar.inc                  |    1 +
 meta/recipes-extended/tar/tar_1.25.bb              |    9 -------
 meta/recipes-extended/tar/tar_1.26.bb              |    9 +++++++
 11 files changed, 32 insertions(+), 29 deletions(-)
 rename meta/recipes-connectivity/openssh/{openssh-5.6p1 => openssh-5.8p2}/init (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.6p1 => openssh-5.8p2}/nostrip.patch (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.6p1 => openssh-5.8p2}/ssh_config (100%)
 rename meta/recipes-connectivity/openssh/{openssh-5.6p1 => openssh-5.8p2}/sshd_config (100%)
 rename meta/recipes-connectivity/openssh/{openssh_5.6p1.bb => openssh_5.8p2.bb} (93%)
 rename meta/recipes-extended/grep/{grep_2.7.bb => grep_2.8.bb} (84%)
 rename meta/recipes-extended/tar/{tar-replacement-native_1.25.bb => tar-replacement-native_1.26.bb} (100%)
 delete mode 100644 meta/recipes-extended/tar/tar_1.25.bb
 create mode 100644 meta/recipes-extended/tar/tar_1.26.bb




             reply	other threads:[~2011-06-06  4:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  4:49 Scott Garman [this message]
2011-06-06  4:49 ` [PATCH 1/4] openssh: upgrade to v5.8p2 Scott Garman
2011-06-06  4:49 ` [PATCH 2/4] grep: upgrade to v2.8 Scott Garman
2011-06-06  4:49 ` [PATCH 3/4] tar: upgrade to v1.26 Scott Garman
2011-06-06  8:00   ` Phil Blundell
2011-06-06 10:46     ` Richard Purdie
2011-06-06 12:09       ` Mark Hatle
2011-06-07  8:24         ` Phil Blundell
2011-06-06  4:49 ` [PATCH 4/4] distro-tracking: update openssh, tar, and grep Scott Garman
2011-06-08 16:51 ` [PATCH 0/4] Recipe upgrades: openssh, grep, tar Saul Wold

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.1307331820.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