From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Recipe upgrades - gzip and sudo
Date: Fri, 22 Jun 2012 10:25:49 -0700 [thread overview]
Message-ID: <cover.1340385690.git.scott.a.garman@intel.com> (raw)
Hello,
These are some trivial recipe upgrades for gzip and sudo. They have
been build-tested for all 5 of our qemu architectures, and I've done
a visual inspection of the package output to watch for any troublesome
differences. (I do intend to start using buildhistory soon)
Note, this pull request is for oe-core master.
Scott
The following changes since commit e2cc4a44d510e0d473d15f207c1c886db6a5ccf7:
[PATCH] guile: fix compilation on MIPS/PPC (2012-06-21 13:41:12 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sgarman/recipe-upgrades-oe
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades-oe
Scott Garman (2):
gzip: upgrade to 1.5
sudo: upgrade to 1.8.5p2
meta/recipes-extended/gzip/gzip.inc | 7 +++++--
meta/recipes-extended/gzip/gzip_1.4.bb | 10 ----------
meta/recipes-extended/gzip/gzip_1.5.bb | 10 ++++++++++
meta/recipes-extended/sudo/sudo.inc | 2 +-
.../sudo/{sudo_1.8.4p4.bb => sudo_1.8.5p2.bb} | 6 +++---
5 files changed, 19 insertions(+), 16 deletions(-)
delete mode 100644 meta/recipes-extended/gzip/gzip_1.4.bb
create mode 100644 meta/recipes-extended/gzip/gzip_1.5.bb
rename meta/recipes-extended/sudo/{sudo_1.8.4p4.bb => sudo_1.8.5p2.bb} (83%)
--
1.7.9.5
next reply other threads:[~2012-06-22 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 17:25 Scott Garman [this message]
2012-06-22 17:25 ` [PATCH 1/2] gzip: upgrade to 1.5 Scott Garman
2012-06-23 4:56 ` Saul Wold
2012-06-25 15:36 ` Scott Garman
2012-06-22 17:25 ` [PATCH 2/2] sudo: upgrade to 1.8.5p2 Scott Garman
2012-06-25 16:26 ` [PATCH 0/2] Recipe upgrades - gzip and sudo 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.1340385690.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