From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Scott Garman <scott.a.garman@intel.com>
Subject: Re: [PATCH 0/4] Recipe upgrades - sudo, at, base-passwd
Date: Mon, 19 Mar 2012 09:22:27 -0700 [thread overview]
Message-ID: <4F675D43.1000605@linux.intel.com> (raw)
In-Reply-To: <cover.1331824888.git.scott.a.garman@intel.com>
On 03/15/2012 08:22 AM, Scott Garman wrote:
> Hello,
>
> Here are some recipe upgrades for sudo, at, and base-passwd.
>
> These recipes have been build tested on all 5 of our qemu architectures.
> I have also done a visual inspection of the image and package output
> between the previous and new versions of each recipe to check for
> potential errors.
>
> The following changes since commit d4f1ef6b8297826230a68e535098709d07de1f48:
>
> qt4: package static libraries correctly to fix warnings (2012-03-15 13:33:37 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib sgarman/recipe-upgrades2-oe
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades2-oesgarman/recipe-upgrades2-oe
>
> Scott Garman (4):
> sudo: upgrade to 1.8.4p4
> at: upgrade to 3.1.13
> base-passwd: upgrade to 3.5.24
> distro_tracking: update sudo, at, base-passwd
>
> .../conf/distro/include/distro_tracking_fields.inc | 24 +++++++++---------
> .../nobash.patch | 0
> .../root-home.patch | 0
> ...base-passwd_3.5.22.bb => base-passwd_3.5.24.bb} | 16 ++++++------
> .../at/{at_3.1.12.bb => at_3.1.13.bb} | 13 ++++-----
> .../configure-add-enable-pam.patch | 0
> .../at/{at-3.1.12 => files}/configure.patch | 0
> .../fix_parallel_build_error.patch | 0
> .../at/files/nonstripbinaries.patch | 26 --------------------
> .../at/{at-3.1.12 => files}/pam.conf.patch | 0
> meta/recipes-extended/at/files/use-ldflags.patch | 5 ++-
> .../sudo/{sudo_1.8.4.bb => sudo_1.8.4p4.bb} | 6 ++--
> 12 files changed, 32 insertions(+), 58 deletions(-)
> rename meta/recipes-core/base-passwd/{base-passwd-3.5.22 => base-passwd-3.5.24}/nobash.patch (100%)
> rename meta/recipes-core/base-passwd/{base-passwd-3.5.22 => base-passwd-3.5.24}/root-home.patch (100%)
> rename meta/recipes-core/base-passwd/{base-passwd_3.5.22.bb => base-passwd_3.5.24.bb} (95%)
> rename meta/recipes-extended/at/{at_3.1.12.bb => at_3.1.13.bb} (88%)
> rename meta/recipes-extended/at/{at-3.1.12 => files}/configure-add-enable-pam.patch (100%)
> rename meta/recipes-extended/at/{at-3.1.12 => files}/configure.patch (100%)
> rename meta/recipes-extended/at/{at-3.1.12 => files}/fix_parallel_build_error.patch (100%)
> delete mode 100644 meta/recipes-extended/at/files/nonstripbinaries.patch
> rename meta/recipes-extended/at/{at-3.1.12 => files}/pam.conf.patch (100%)
> rename meta/recipes-extended/sudo/{sudo_1.8.4.bb => sudo_1.8.4p4.bb} (83%)
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-19 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 15:22 [PATCH 0/4] Recipe upgrades - sudo, at, base-passwd Scott Garman
2012-03-15 15:22 ` [PATCH 1/4] sudo: upgrade to 1.8.4p4 Scott Garman
2012-03-15 15:22 ` [PATCH 2/4] at: upgrade to 3.1.13 Scott Garman
2012-03-15 15:22 ` [PATCH 3/4] base-passwd: upgrade to 3.5.24 Scott Garman
2012-03-15 15:22 ` [PATCH 4/4] distro_tracking: update sudo, at, base-passwd Scott Garman
2012-03-19 16:22 ` Saul Wold [this message]
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=4F675D43.1000605@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.com \
/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