From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] shadow: Fix rpm failed dependencies when install
Date: Wed, 31 Aug 2011 19:58:38 +0100 [thread overview]
Message-ID: <1314817118.5939.479.camel@rex> (raw)
In-Reply-To: <d241a9acdd1578fb711d6d7c113cc51eb1bea74c.1314691314.git.edwin.zhai@intel.com>
On Tue, 2011-08-30 at 16:05 +0800, edwin.zhai@intel.com wrote:
> From: Zhai Edwin <edwin.zhai@intel.com>
>
> There are some links become invalid after rename, so that failed dependencies
> detected when install rpm package. This commit update links to resolve it.
>
> [YOCTO #1158] got fixed.
>
> Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
> ---
> meta/recipes-extended/shadow/shadow_4.1.4.3.bb | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-08-31 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 8:05 [PATCH 0/1] shadow: Fix rpm package install failure, Edwin, Aug30, 2011 edwin.zhai
2011-08-30 8:05 ` [PATCH 1/1] shadow: Fix rpm failed dependencies when install edwin.zhai
2011-08-31 18:58 ` Richard Purdie [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=1314817118.5939.479.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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