From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: clarify the file_contexts.subs_dist configuration file usage
Date: Wed, 15 Aug 2012 10:45:48 +0200 [thread overview]
Message-ID: <20120815084548.GA2701@siphos.be> (raw)
In-Reply-To: <502B6010.1060007@trentalancia.com>
On Wed, Aug 15, 2012 at 10:38:40AM +0200, Guido Trentalancia wrote:
> You may have a broken version of the userspace tools.
>
> I have just tested again and the copy of semanage that I have runs fine
> the above mentioned test.
>
> The version of semanage I am using should be dated June 2012, if that
> helps...
>
> It's important to keep that note in my opinion, because otherwise it
> tends to generate confusion due to the somewhat unfortunate name that
> has been chosen for the file and due to the lack of a specific
> (userspace) manual page.
The latest release of policycoreutils is from 2012-02-16
(policycoreutils-2.1.10). The one I have is that version, plus a few
python-3 supporting fixes. I tried it with Python-2.7 to be sure, but got
the same result.
Perhaps your distribution has fixes to it that haven't been made upstream
yet (or not in a stable release)?
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2012-08-15 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 13:13 [refpolicy] [PATCH]: clarify the file_contexts.subs_dist configuration file usage Guido Trentalancia
2012-08-14 12:03 ` Christopher J. PeBenito
2012-08-15 8:02 ` Sven Vermeulen
2012-08-15 8:13 ` Guido Trentalancia
2012-08-15 8:20 ` Sven Vermeulen
2012-08-15 8:38 ` Guido Trentalancia
2012-08-15 8:45 ` Sven Vermeulen [this message]
2012-08-15 9:48 ` Guido Trentalancia
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 12:30 Guido Trentalancia
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=20120815084548.GA2701@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.