Description of problem: Found by /CoreOS/policycoreutils/Regression/bz588280-sepolgen-ifgen-traceback Version-Release number of selected component (if applicable): selinux-policy-devel-2.4.6-300.el5 How reproducible: always Steps to Reproduce: # sepolgen-ifgen -i /usr/share/selinux/devel/include/apps/thunderbird.if Syntax error on line 1 ` [type=TICK] # echo $? 0 # sepolgen-ifgen -v -i /usr/share/selinux/devel/include/apps/thunderbird.if Parsing support macros (/usr/share/selinux/devel/include/support/obj_perm_sets.spt): done. Parsing interface files: %--10---20---30---40---50---60---70---80---90--100 Syntax error on line 1 ` [type=TICK] error parsing file /usr/share/selinux/devel/include/apps/thunderbird.if: could not parse text: "Syntax error on line 1 ` [type=TICK]" failed to parse some headers: /usr/share/selinux/devel/include/apps/thunderbird.if # echo $? 0 Actual results: Expected results:
This is a syntax error --optinal_policy(` allow $1_t $2_dbusd_t:dbus send_msg; ++optional_policy(` allow $1_t $2_dbusd_t:dbus send_msg;
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release.
Fixed in selinux-policy-2.4.6-301.el5
I see syntax errors when following files are processed: ./include/system/init.if ./include/services/inetd.if
Fixed in selinux-policy-2.4.6-306.el5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1069.html