refpolicy build failures
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.
Could you have a look?
Thanks a lot,
Thomas Petazzoni
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com _______________________________________________ buildroot mailing list [email protected] http://lists.busybox.net/mailman/listinfo/buildroot
Hello Thomas,
Quoted 10 lines · Thomas Petazzoni
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.
Quoted 10 lines
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
[email protected]
http://lists.busybox.net/mailman/listinfo/buildroot
Hello Fabrice,
Quoted 1 line · On Sat, 31 Jul 2021 10:05:50 +0200 Fabrice Fontaine…
I fixed minidlna, fetchmail and exim.
Thanks for your work, I merged your patches fixing these issues.
Quoted 7 lines
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
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com _______________________________________________ buildroot mailing list [email protected] http://lists.busybox.net/mailman/listinfo/buildroot
Quoted 18 lines · Thomas Petazzoni
Hello Fabrice,
Quoted 1 line · On Sat, 31 Jul 2021 10:05:50 +0200 Fabrice Fontaine…
I fixed minidlna, fetchmail and exim.
Thanks for your work, I merged your patches fixing these issues.
Quoted 7 lines
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.
Quoted 3 lines
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.
Indeed, I'll send patches to add apache/httpd. Hopefully, we should be able to remove it later on.
Quoted 8 lines
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Best Regards,
Fabrice
_______________________________________________
buildroot mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/buildroot