Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Patches,
	discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package_rpm: Fix useradd preinst ordering issues
Date: Thu, 12 Apr 2012 12:11:04 -0500	[thread overview]
Message-ID: <4F870CA8.9070709@windriver.com> (raw)
In-Reply-To: <CAGDS+nk+yTmthqFi+EeC9FZY49Fyiuyis1F3B-1+daa_tYpBEw@mail.gmail.com>

On 4/12/12 12:06 PM, Steve Sakoman wrote:
> On Thu, Apr 12, 2012 at 9:08 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org>  wrote:
>
>> For what its worth, bash here does Provides: /bin/sh so I'm a little
>> puzzled about what is going on here. If its not doing that, it would
>> certainly cause the error you're reporting...
>
> Hmm . . . while I see:
>
> Provides: /bin/sh
>
> in bash.spec, it is a different story in the pkgdata/runtime files.
>
> busybox has:
>
> FILERPROVIDES_/bin/busybox_busybox:<snip many filenames>  /bin/sh
> <snip many filenames>
>
> While bash doesn't have a FILERPROVIDES entry at all.
>
> Could this be why rpm doesn't realize bash provides /bin/sh?

They should both be equally valid for the purpose of dependency resolution.

--Mark

> Steve




  reply	other threads:[~2012-04-12 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 21:31 [PATCH] package_rpm: Fix useradd preinst ordering issues Richard Purdie
2012-04-11 21:42 ` Mark Hatle
2012-04-12 13:39   ` Steve Sakoman
2012-04-12 15:36     ` Steve Sakoman
2012-04-12 15:46       ` Mark Hatle
2012-04-12 15:55         ` Steve Sakoman
2012-04-12 16:08           ` Richard Purdie
2012-04-12 17:06             ` Steve Sakoman
2012-04-12 17:11               ` Mark Hatle [this message]
2012-04-12 16:37           ` Mark Hatle
2012-04-12 16:47             ` Steve Sakoman

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=4F870CA8.9070709@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sakoman@gmail.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