Poky Project Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 0/4] Recipe upgrades: sudo, libpam, and mtools
Date: Thu, 02 Dec 2010 09:50:03 -0800	[thread overview]
Message-ID: <4CF7DC4B.5030601@intel.com> (raw)
In-Reply-To: <cover.1290624288.git.scott.a.garman@intel.com>

On 11/24/2010 10:44 AM, Scott Garman wrote:
> Hi Saul,
>
> Here are a few distro recipe upgrades. Some things to note:
>
> * The version of mtools we have had to date is a GPLv2 version, so I
>    left that recipe as-is and added the latest release, which is GPLv3.
> * I've added source checksums, LIC_FILES_CHKSUM, and SUMMARY fields
>    where needed, etc.
> * I was able to remove obsolete patches from sudo and libpam after
>    doing close verification.
> * I have successfully built these on all of our nightly-release qemu
>    machine arches - build testing should be solid. I also verfied the
>    output of the final packages to check for missing files or other
>    significant changes.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: sgarman/recipe-upgrades
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades
>
> Thanks,
>      Scott Garman<scott.a.garman@intel.com>
> ---
>
>
> Scott Garman (4):
>    sudo: upgrade to version 1.7.4p4
>    libpam: upgrade to version 1.1.3
>    mtools: add version 4.0.15
>    distro_tracking_fields.inc: update sudo, libpam, and mtools
>
>   .../conf/distro/include/distro_tracking_fields.inc |   31 +++--
>   .../mtools/mtools/no-x11.gplv3.patch               |   15 ++
>   meta/recipes-devtools/mtools/mtools_4.0.15.bb      |   21 +++
>   .../pam/libpam-1.1.1/disable_crossbinary.patch     |   34 -----
>   .../pam/{libpam-1.1.1 =>  libpam}/99_pam            |    0
>   .../{libpam-1.1.1 =>  libpam}/pam.d/common-account  |    0
>   .../pam/{libpam-1.1.1 =>  libpam}/pam.d/common-auth |    0
>   .../{libpam-1.1.1 =>  libpam}/pam.d/common-password |    0
>   .../{libpam-1.1.1 =>  libpam}/pam.d/common-session  |    0
>   .../pam.d/common-session-noninteractive            |    0
>   .../pam/{libpam-1.1.1 =>  libpam}/pam.d/other       |    0
>   .../pam/{libpam_1.1.1.bb =>  libpam_1.1.3.bb}       |   12 ++-
>   meta/recipes-extended/sudo/files/autofoo.patch     |  143 --------------------
>   meta/recipes-extended/sudo/files/libtool.patch     |   20 +++
>   meta/recipes-extended/sudo/files/noexec-link.patch |   17 ---
>   meta/recipes-extended/sudo/files/nostrip.patch     |   23 ---
>   meta/recipes-extended/sudo/site/bit-32             |    2 -
>   meta/recipes-extended/sudo/site/bit-64             |    2 -
>   meta/recipes-extended/sudo/sudo.inc                |   21 ++--
>   meta/recipes-extended/sudo/sudo_1.7.2p7.bb         |    7 -
>   meta/recipes-extended/sudo/sudo_1.7.4p4.bb         |   11 ++
>   21 files changed, 102 insertions(+), 257 deletions(-)
>   create mode 100644 meta/recipes-devtools/mtools/mtools/no-x11.gplv3.patch
>   create mode 100644 meta/recipes-devtools/mtools/mtools_4.0.15.bb
>   delete mode 100644 meta/recipes-extended/pam/libpam-1.1.1/disable_crossbinary.patch
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/99_pam (100%)
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/pam.d/common-account (100%)
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/pam.d/common-auth (100%)
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/pam.d/common-password (100%)
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/pam.d/common-session (100%)
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/pam.d/common-session-noninteractive (100%)
>   rename meta/recipes-extended/pam/{libpam-1.1.1 =>  libpam}/pam.d/other (100%)
>   rename meta/recipes-extended/pam/{libpam_1.1.1.bb =>  libpam_1.1.3.bb} (89%)
>   delete mode 100644 meta/recipes-extended/sudo/files/autofoo.patch
>   create mode 100644 meta/recipes-extended/sudo/files/libtool.patch
>   delete mode 100644 meta/recipes-extended/sudo/files/noexec-link.patch
>   delete mode 100644 meta/recipes-extended/sudo/files/nostrip.patch
>   delete mode 100644 meta/recipes-extended/sudo/site/bit-32
>   delete mode 100644 meta/recipes-extended/sudo/site/bit-64
>   delete mode 100644 meta/recipes-extended/sudo/sudo_1.7.2p7.bb
>   create mode 100644 meta/recipes-extended/sudo/sudo_1.7.4p4.bb
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Pull into Master

Thanks
    Sau!



      parent reply	other threads:[~2010-12-02 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 18:44 [PATCH 0/4] Recipe upgrades: sudo, libpam, and mtools Scott Garman
2010-11-23  5:01 ` [PATCH 1/4] sudo: upgrade to version 1.7.4p4 Scott Garman
2010-11-23 22:45 ` [PATCH 3/4] mtools: add version 4.0.15 Scott Garman
2010-11-24  0:41 ` [PATCH 2/4] libpam: upgrade to version 1.1.3 Scott Garman
2010-11-24 18:42 ` [PATCH 4/4] distro_tracking_fields.inc: update sudo, libpam, and mtools Scott Garman
2010-12-02 17:50 ` 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=4CF7DC4B.5030601@intel.com \
    --to=saul.wold@intel.com \
    --cc=poky@yoctoproject.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