All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Build of 20120215 fails with unknown role system_r
Date: Sat, 25 Feb 2012 11:05:47 +0100	[thread overview]
Message-ID: <20120225100547.GA28560@siphos.be> (raw)

While trying to build the 20120215 reference policy, I hit the following
problem while running "make base":

Compiling strict base module
/usr/bin/checkmodule:  loading policy configuration from base.conf
policy/modules/admin/bootloader.te":9:ERROR 'unknown role system_r' at token
';' on line 40265:
# this line was moved by the build process: attribute_role bootloader_roles;
roleattribute system_r bootloader_roles;
/usr/bin/checkmodule:  error(s) encountered while parsing configuration
make: *** [tmp/base.mod] Error 1

All utilities have been updated with the latest userspace release. Is the
system role defined somewhere that I forgot to include in my modules.conf? I
have the following modules marked for base:

application authlogin bootloader clock consoletype corecommands corenetwork
cron devices dmesg domain files filesystem fstools getty hostname hotplug
init iptables kernel libraries locallogin logging lvm miscfiles mcs mls
modutils mount mta netutils nscd portage raid rsync selinux selinuxutil ssh
staff storage su sysadm sysnetwork terminal ubac udev userdomain usermanage
unprivuser

Wkr,
	Sven Vermeulen

             reply	other threads:[~2012-02-25 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 10:05 Sven Vermeulen [this message]
2012-02-26  9:26 ` [refpolicy] Build of 20120215 fails with unknown role system_r Harry Ciao
2012-02-26 12:24   ` Sven Vermeulen
2012-02-27 15:06     ` Christopher J. PeBenito
2012-02-28 10:43   ` Harry Ciao
2012-02-29  8:12 ` Harry Ciao

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=20120225100547.GA28560@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.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.