Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libsemanage: define installation location of semanage.conf for host
Date: Tue, 13 Nov 2018 21:22:29 +0100	[thread overview]
Message-ID: <20181113212229.3254c6f4@windsurf> (raw)
In-Reply-To: <20181109215730.30795-1-thomas.petazzoni@bootlin.com>

Hello,

On Fri,  9 Nov 2018 22:57:30 +0100, Thomas Petazzoni wrote:
> When /etc/selinux/semanage.conf does not exist, libsemanage tries to
> overwrite it. For the target package, it works fine because $(DESTDIR)
> is taken into account.
> 
> However, for the host package, $(DESTDIR) is empty, and the location
> used for /etc/selinux/semanage.conf is not affected by $(PREFIX). This
> causes host-libsemanage to try to install /etc/selinux/semanage.conf,
> which obviously fails with:
> 
>   test -f /etc/selinux/semanage.conf || install -m 644 -D semanage.conf /etc/selinux/semanage.conf
>   install: cannot create directory '/etc/selinux': Permission denied
> 
> To fix this, this commit passes DEFAULT_SEMANAGE_CONF_LOCATION in the
> make options when building/installing host-libsemanage, providing a
> path to semanage.conf that Buildroot can write to.
> 
> Fixes:
> 
>   http://autobuild.buildroot.net/results/cd27e3c66274622d0c3dd5a601a36efb1bc45011/
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
>  package/libsemanage/libsemanage.mk | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-11-13 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 21:57 [Buildroot] [PATCH] libsemanage: define installation location of semanage.conf for host Thomas Petazzoni
2018-11-12 14:42 ` Matthew Weber
2018-11-13 20:22 ` Thomas Petazzoni [this message]
2018-11-26 11:44 ` Peter Korsgaard

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=20181113212229.3254c6f4@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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