From: Stephen Smalley <sds@tycho.nsa.gov>
To: russell@coker.com.au
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: global name 'seinfo' is not defined
Date: Mon, 19 Mar 2012 08:11:48 -0400 [thread overview]
Message-ID: <1332159108.23035.1.camel@moss-pluto> (raw)
In-Reply-To: <201203191716.19321.russell@coker.com.au>
On Mon, 2012-03-19 at 17:16 +1100, Russell Coker wrote:
> I'm stuck on the following error after updating the Debian packages to the
> latest userspace. Could someone please tell me where this "seinfo" function
> is supposed to be defined? I can probably work out the cause of this if I
> could find where it's defined.
setools (setools-libs-python in Fedora).
>
> As an aside, if someone who's good at Python wants to help out with the Debian
> SE Linux work then that would be greatly appreciated. Not much work is
> required, but it's tough for people like me who generally don't do Python.
>
>
> # dmesg|audit2allow
> Traceback (most recent call last):
> File "/usr/bin/audit2allow", line 354, in <module>
> app.main()
> File "/usr/bin/audit2allow", line 345, in main
> self.__output()
> File "/usr/bin/audit2allow", line 315, in __output
> g.add_access(self.__avs)
> File "/usr/lib/python2.7/dist-packages/sepolgen/policygen.py", line 211, in
> add_access
> self.__add_allow_rules(raw_allow)
> File "/usr/lib/python2.7/dist-packages/sepolgen/policygen.py", line 179, in
> __add_allow_rules
> self.domains = seinfo(ATTRIBUTE, name="domain")[0]["types"]
> NameError: global name 'seinfo' is not defined
>
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2012-03-19 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 6:16 global name 'seinfo' is not defined Russell Coker
2012-03-19 12:11 ` Stephen Smalley [this message]
2012-03-19 13:49 ` Daniel J Walsh
2012-03-19 14:23 ` lkcl luke
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=1332159108.23035.1.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.