From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
To: <poky@yoctoproject.org>
Subject: [PATCH 0/1]sudo.inc:Add directory "/var/lib" to sudo.inc in the stage of do_install_prepend
Date: Mon, 30 May 2011 16:35:54 +0800 [thread overview]
Message-ID: <cover.1306726421.git.xiaofeng.yan@windriver.com> (raw)
From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
Hi Saul & Richard
I have added some comment in the recipe about why this is necessary as
someone could easily look at it and decide it wasn't needed according to Richard's requirement.
Pervious email content:
I submit this patch to fix [YOCTO #1092].
LSB Test Suite check access permission of directory "/var/lib". The current access permission is "0700".
This is because:
$(SHELL) $(srcdir)/mkinstalldirs -m 0700 $(DESTDIR)$(timedir)
and the timedir=/var/lib/sudo
but if /var/lib doesn't exist, the mkinstalldirs would create it and set the
mode to 0700 recursively, so all of the /var, /var/lib and /var/lib/sudo would
be set to 0700, but what sudo needs is only set /var/lib/sudo to 0700.
So LSB Test Suite recognizes it as a bug. Other images including sudo could have no this problem because after installing sudo package other package operate on directory "/var/lib" but for lsb image sudo package is the last package which operate on directory "/var/lib"
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/sudo
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/sudo
Thanks,
Xiaofeng Yan <xiaofeng.yan@windriver.com>
---
Xiaofeng Yan (1):
sudo.inc: Add do_install_prepend () to sudo.inc
meta/recipes-extended/sudo/sudo.inc | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
next reply other threads:[~2011-05-30 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 8:35 Xiaofeng Yan [this message]
2011-05-30 8:35 ` [PATCH 1/1] sudo.inc: Add do_install_prepend () to sudo.inc Xiaofeng Yan
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.1306726421.git.xiaofeng.yan@windriver.com \
--to=xiaofeng.yan@windriver.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.