From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Antoine Tenart <atenart@kernel.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/refpolicy: fix build with smartmontools
Date: Wed, 29 Nov 2023 10:00:21 +0100 [thread overview]
Message-ID: <87wmu19boa.fsf@48ers.dk> (raw)
In-Reply-To: <20231128214841.1045878-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Tue, 28 Nov 2023 22:48:41 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix the following build failure with smartmontools raised since bump to
> version 2.20231002 in commit 68de45491ba7d4b7aeff6f869934745440f88c00:
> Compiling targeted policy.33
> env LD_LIBRARY_PATH="/home/thomas/autobuild/instance-2/output-1/host/lib:/home/thomas/autobuild/instance-2/output-1/host/usr/lib" /home/thomas/autobuild/instance-2/output-1/host/usr/bin/checkpolicy -c 33 -U deny -S -O -E policy.conf -o policy.33
> policy/modules/services/smartmon.te:146:ERROR 'type fsadm_exec_t is not within scope' at token ';' on line 237472:
> allow smartmon_update_drivedb_t fsadm_exec_t:file { { getattr open map read execute ioctl } ioctl lock execute_no_trans };
> #line 146
> checkpolicy: error(s) encountered while parsing configuration
> make[1]: *** [Rules.monolithic:80: policy.33] Error 1
> Fixes:
> - http://autobuild.buildroot.org/results/a01123de9a8c1927060e7e4748666bebfc82ea44
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-29 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 21:48 [Buildroot] [PATCH 1/1] package/refpolicy: fix build with smartmontools Fabrice Fontaine
2023-11-29 9:00 ` Peter Korsgaard [this message]
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=87wmu19boa.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=atenart@kernel.org \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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.