All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.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:05:50 +0200	[thread overview]
Message-ID: <CAPi7W80D-vTy8Hg7R-aLekkW=F5CopjwkSqjwjzrhh__-4ZunA@mail.gmail.com> (raw)
In-Reply-To: <20210730091005.7c91f3b7@windsurf>

Hello Thomas,

Le ven. 30 juil. 2021 à 09:10, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> a écrit :
>
> Hello Fabrice,
>
> Since you've added lots of SELinux modules to package, we're seeing
> build failures on the refpolicy package:
>
>   http://autobuild.buildroot.net/?reason=refpolicy-2.20210203
>
> There are a least issues with the minidlna, fetchmail and perhaps
> apache/httpd.
I fixed minidlna, fetchmail and exim.
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.
>
> Could you have a look?
>
> Thanks a lot,
>
> Thomas Petazzoni
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
Best Regards,

Fabrice
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-07-31  8:06 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 [this message]
2021-07-31  8:13   ` Thomas Petazzoni
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='CAPi7W80D-vTy8Hg7R-aLekkW=F5CopjwkSqjwjzrhh__-4ZunA@mail.gmail.com' \
    --to=fontaine.fabrice@gmail.com \
    --cc=buildroot@uclibc.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=thomas.petazzoni@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 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.