From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] some Debian specific patches
Date: Thu, 08 Jul 2010 15:45:55 +0200 [thread overview]
Message-ID: <1278596755.2986.116.camel@tesla.lan> (raw)
In-Reply-To: <201007071702.17347.russell@coker.com.au>
On Wed, 07/07/2010 at 17.02 +1000, Russell Coker wrote:
> The attached patch has some Debian specific patches to the policy.
>
> I've put in a couple of ifdef(`distro_redhat' entries, in some of those cases
> we might want to make either the Debian or the Red Hat way the default for
> other distributions.
>
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
After applying the patch I get the following errors (using the latest
release of userspace tools and refpolicy):
/etc/selinux/refpolicy-mcs/contexts/files/file_contexts: Multiple same
specifications for /var/lib/dcc(/.*)?.
/etc/selinux/refpolicy-mcs/contexts/files/file_contexts: Multiple same
specifications for /var/lib/dcc/map.
/etc/selinux/refpolicy-mcs/contexts/files/file_contexts: Invalid
argument
libsemanage.semanage_install_active: setfiles returned error code 1.
/usr/sbin/semodule: Failed!
In fact, after applying the patch the same two definitions are repeated
twice (for the debian define) in policy/modules/services/dcc.fc. Thus
the whole "ifdef(`distro_debian'..." should be probably removed from the
modified version...
Regards,
Guido
next prev parent reply other threads:[~2010-07-08 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 7:02 [refpolicy] some Debian specific patches Russell Coker
2010-07-08 13:45 ` Guido Trentalancia [this message]
2010-07-08 13:53 ` Russell Coker
2010-07-08 14:56 ` Guido Trentalancia
2010-07-11 17:48 ` Martin Orr
2010-07-12 17:52 ` Christopher J. PeBenito
2010-07-17 5:24 ` Russell Coker
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=1278596755.2986.116.camel@tesla.lan \
--to=guido@trentalancia.com \
--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.