From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "buildroot@uclibc.org" <buildroot@uclibc.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [Buildroot] refpolicy build failures
Date: Sat, 31 Jul 2021 10:13:24 +0200 [thread overview]
Message-ID: <20210731101324.54518fbb@windsurf> (raw)
In-Reply-To: <CAPi7W80D-vTy8Hg7R-aLekkW=F5CopjwkSqjwjzrhh__-4ZunA@mail.gmail.com>
Hello Fabrice,
On Sat, 31 Jul 2021 10:05:50 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> I fixed minidlna, fetchmail and exim.
Thanks for your work, I merged your patches fixing these issues.
> The other build failures are all related to packages that can
> optionally share content through apache/httpd (e.g. collectd, cvs,
> git, nut, etc.).
> They're raised when apache is not enabled because their file contexts
> unconditionally use apache/httpd parameters.
> I opened an issue to know how to properly fix those issues:
> https://github.com/SELinuxProject/refpolicy/issues/400.
Should we revert those changes in Buildroot for the time being? Or
unconditionally add the apache/httpd SELinux modules in collectd, cvs,
git, nut ? This is effectively what the refpolicy requires right now.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-31 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 7:10 [Buildroot] refpolicy build failures Thomas Petazzoni
2021-07-31 8:05 ` Fabrice Fontaine
2021-07-31 8:13 ` Thomas Petazzoni [this message]
2021-07-31 8:18 ` Fabrice Fontaine
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=20210731101324.54518fbb@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@uclibc.org \
--cc=fontaine.fabrice@gmail.com \
--cc=maxime.chevallier@bootlin.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