Andre Robatino (robatino(a)fedoraproject.org) said:
> Look at the scripts for the packages in your transaction (rpm -q
> <...>), audit them for syntax errors.
Finally found that on Rawhide, it was simple-scan, already reported as
. On today's F16 updates, I
saw the error twice, once referring to line 1, and once to line 2. One of those
was simple-scan again, I'm not sure about the other but I found errors in
selinux-policy and selinux-policy-targeted and reported them as
. I wish there was an easier
way to find these if they're going to be happening this often.
The best way is to have the full transaction log and then you can reasonably
pinpoint the package based on where you got the message. Unless, of course,
it's an error in %posttrans.
RPM has the information as to what it's running a script from... perhaps
file a RFE to expose it?