From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] Recipe upgrades
Date: Tue, 25 Oct 2011 14:32:44 -0700 [thread overview]
Message-ID: <cover.1319576293.git.scott.a.garman@intel.com> (raw)
Hello,
Here is a set of some straightfoward recipe upgrades: sudo, grep,
mtools, and openssh.
Build testing: These have been successfully built for all 5 qemu
architectures.
Runtime testing: I have performed basic runtime testing for all of
these recipe upgrades as well within a qemux86 session.
The following changes since commit f586aaa8d00361a9597a546d665077c75cf4d520:
libxml-parser-perl, libxml-simple-perl, expat, sgmlspl-native, git: bump PR to rebuild after perl upgrade (2011-10-25 08:36:01 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib sgarman/recipe-upgrades-final
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades-final
Scott Garman (5):
sudo: upgrade to 1.8.3
grep: upgrade to 2.9
mtools: upgrade to 4.0.17
openssh: upgrade to 5.9p1
distro_tracking_fields: updates for sudo, mtools, grep, and openssh
.../conf/distro/include/distro_tracking_fields.inc | 32 ++++++++++----------
.../openssh/{openssh-5.8p2 => openssh-5.9p1}/init | 0
.../{openssh-5.8p2 => openssh-5.9p1}/nostrip.patch | 0
.../{openssh-5.8p2 => openssh-5.9p1}/ssh_config | 0
.../openssh/{openssh-5.8p2 => openssh-5.9p1}/sshd | 0
.../{openssh-5.8p2 => openssh-5.9p1}/sshd_config | 0
.../openssh/{openssh_5.8p2.bb => openssh_5.9p1.bb} | 4 +-
.../mtools/{mtools_4.0.16.bb => mtools_4.0.17.bb} | 4 +-
.../grep/{grep_2.8.bb => grep_2.9.bb} | 4 +-
.../sudo/{sudo_1.8.1p2.bb => sudo_1.8.3.bb} | 6 ++--
10 files changed, 25 insertions(+), 25 deletions(-)
rename meta/recipes-connectivity/openssh/{openssh-5.8p2 => openssh-5.9p1}/init (100%)
rename meta/recipes-connectivity/openssh/{openssh-5.8p2 => openssh-5.9p1}/nostrip.patch (100%)
rename meta/recipes-connectivity/openssh/{openssh-5.8p2 => openssh-5.9p1}/ssh_config (100%)
rename meta/recipes-connectivity/openssh/{openssh-5.8p2 => openssh-5.9p1}/sshd (100%)
rename meta/recipes-connectivity/openssh/{openssh-5.8p2 => openssh-5.9p1}/sshd_config (100%)
rename meta/recipes-connectivity/openssh/{openssh_5.8p2.bb => openssh_5.9p1.bb} (96%)
rename meta/recipes-devtools/mtools/{mtools_4.0.16.bb => mtools_4.0.17.bb} (80%)
rename meta/recipes-extended/grep/{grep_2.8.bb => grep_2.9.bb} (88%)
rename meta/recipes-extended/sudo/{sudo_1.8.1p2.bb => sudo_1.8.3.bb} (82%)
--
1.7.5.4
next reply other threads:[~2011-10-25 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 21:32 Scott Garman [this message]
2011-10-25 21:32 ` [PATCH 1/5] sudo: upgrade to 1.8.3 Scott Garman
2011-10-25 21:32 ` [PATCH 2/5] grep: upgrade to 2.9 Scott Garman
2011-10-25 21:36 ` [PATCH 3/5] mtools: upgrade to 4.0.17 Scott Garman
2011-10-25 21:36 ` [PATCH 4/5] openssh: upgrade to 5.9p1 Scott Garman
2011-10-25 21:36 ` [PATCH 5/5] distro_tracking_fields: updates for sudo, mtools, grep, and openssh Scott Garman
2011-10-26 20:37 ` Saul Wold
2011-10-31 9:08 ` Paul Eggleton
2011-10-31 15:46 ` Saul Wold
2011-10-31 16:05 ` Koen Kooi
2011-11-01 11:38 ` Paul Eggleton
2011-10-27 7:31 ` [PATCH 0/5] Recipe upgrades Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2021-06-06 22:20 Tim Orling
2011-10-18 20:14 [PATCH 0/5] recipe upgrades nitin.a.kamble
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.1319576293.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