Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 512267 - SyntaxError: invalid syntax if self.a1 and int(self.a1) & O_ACCMODE) != os.O_RDONLY:
Summary: SyntaxError: invalid syntax if self.a1 and int(self.a1) & O_ACCMODE) != os.O_...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
 
Reported: 2009-07-16 21:50 UTC by Nicolas Mailhot
Modified: 2009-07-19 16:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-19 16:16:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nicolas Mailhot 2009-07-16 21:50:47 UTC
$ sealert
Traceback (most recent call last):
  File "/usr/bin/sealert", line 109, in <module>
    from setroubleshoot.signature import *
  File "/usr/lib64/python2.6/site-packages/setroubleshoot/signature.py", line 61, in <module>
    from setroubleshoot.audit_data import *
  File "/usr/lib64/python2.6/site-packages/setroubleshoot/audit_data.py", line 623
    if self.a1 and int(self.a1) & O_ACCMODE) != os.O_RDONLY:
                                           ^
SyntaxError: invalid syntax

libselinux-2.0.85-1.fc12.x86_64
libselinux-debuginfo-2.0.85-1.fc12.x86_64
libselinux-python-2.0.85-1.fc12.x86_64
libselinux-utils-2.0.85-1.fc12.x86_64
selinux-policy-3.6.22-1.fc12.noarch
selinux-policy-targeted-3.6.22-1.fc12.noarch
setroubleshoot-server-2.2.14-1.fc12.x86_64

Comment 1 Daniel Walsh 2009-07-19 16:16:06 UTC
Fixed in setroubleshoot-server-2.2.15-1.fc12.x86_64


Note You need to log in before you can comment on or make changes to this bug.