From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [1/1] sudo: fixed wrong `chmod` path
Date: Fri, 25 May 2012 09:41:44 -0700 [thread overview]
Message-ID: <4FBFB648.1070403@linux.intel.com> (raw)
In-Reply-To: <6b907017a92c4178980b18fbe2fef47cbd2b1a34.1337519599.git.mihaix.lindner@linux.intel.com>
On 05/24/2012 10:19 AM, Mihai Lindner wrote:
> Placed $D between braces ${D} to be correctly expanded to the
> workdir path, instead of a path relative to host rootfs.
> Currently, bitbake sudo fails on host systems where sudo is not
> installed.
>
> Signed-off-by: Mihai Lindner<mihaix.lindner@linux.intel.com>
>
> ---
> meta/recipes-extended/sudo/sudo_1.8.4p4.bb | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-extended/sudo/sudo_1.8.4p4.bb b/meta/recipes-extended/sudo/sudo_1.8.4p4.bb
> index 2315322..20c4a14 100644
> --- a/meta/recipes-extended/sudo/sudo_1.8.4p4.bb
> +++ b/meta/recipes-extended/sudo/sudo_1.8.4p4.bb
> @@ -1,6 +1,6 @@
> require sudo.inc
>
> -PR = "r0"
> +PR = "r1"
>
> SRC_URI = "http://ftp.sudo.ws/sudo/dist/sudo-${PV}.tar.gz \
> file://libtool.patch \
> @@ -24,6 +24,6 @@ do_install_append () {
> fi
> done
>
> - chmod 4111 $D/usr/bin/sudo
> - chmod 0440 $D/etc/sudoers
> + chmod 4111 ${D}/usr/bin/sudo
> + chmod 0440 ${D}/etc/sudoers
> }
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-05-25 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 13:17 [1/1] sudo: fixed wrong `chmod` path Mihai Lindner
2012-05-25 16:41 ` 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=4FBFB648.1070403@linux.intel.com \
--to=sgw@linux.intel.com \
--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