Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com, saul.wold@intel.com
Subject: [PATCH 0/1] libpam: QA issue: installed in the base_prefix, requires a shared library under exec_prefix
Date: Thu, 22 Nov 2012 15:56:31 +0800	[thread overview]
Message-ID: <cover.1353570517.git.jackie.huang@windriver.com> (raw)

From: Jackie Huang <jackie.huang@windriver.com>

We added the fix for zlib 1.2.6 and cracklib 2.8.18 as bbappends in our own layer and worked well,
but when they are updated in oe-core, the bbappends became dangling, so if the fix is
accepted in or-core, we don't have to mantain and update the bbappends and clean them up,
thanks!

Also added the author of the fix in CC list.

* Test info:
1) MACHINE=qemux86-64/qemux86/qemuppc
$ bitbake core-image-sato 
$ bitbake libpam

The following changes since commit 654d5816f8ff696d42d72cfb881d5e51330a79b6:

  build-appliance-image: Update to dee77eca39f406f90e60d9c5ef7a66fcc8f57dbf commit (2012-11-21 20:38:47 +0000)

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

Jackie Huang (1):
  libpam: QA Issue: installed in the base_prefix, requires a shared
    library under exec_prefix

 meta/recipes-core/zlib/zlib_1.2.7.bb              |   11 +++++++++++
 meta/recipes-extended/cracklib/cracklib_2.8.19.bb |    9 +++++++--
 2 files changed, 18 insertions(+), 2 deletions(-)

-- 
1.7.4




             reply	other threads:[~2012-11-22  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22  7:56 jackie.huang [this message]
2012-11-22  7:56 ` [PATCH 1/1] libpam: QA Issue: installed in the base_prefix, requires a shared library under exec_prefix jackie.huang

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.1353570517.git.jackie.huang@windriver.com \
    --to=jackie.huang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@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