Description of problem: In selinux-policy-3.10.0-32.fc16.noarch's postuninstall scriptlet: if [ $1 = 0 ]; then In selinux-policy-targeted-3.10.0-32.fc16.noarch's postinstall scriptlet: if [ $? = 0 -a "${SELINUXTYPE}" = targeted -a -f ${FILE_CONTEXT}.pre ]; then Version-Release number of selected component (if applicable): selinux-policy-3.10.0-32.fc16.noarch
Same problem in selinux-policy-3.10.0-31.fc17.noarch and selinux-policy-targeted-3.10.0-31.fc17.noarch in Rawhide.
Actually, I'm not sure this is a bug anymore (bash syntax isn't the same as C regarding the use of the = sign, it appears to be legitimate when doing string comparisons). Can someone check if this is a bug?
Looking more like a false alarm as the same syntax occurs in F15's selinux-policy* packages. But I'll wait for someone to confirm before closing.
Yes, this is ok. Closing this bug.
This is the equivalent of doing the test command man test ... STRING1 = STRING2 the strings are equal