https://bugzilla.redhat.com/show_bug.cgi?id=561579 setroubleshoot_trace_hash:fac7daa743f48e84b0f1adddd13eaffce1b2c8dc6a173b5aef41026d43819c99 https://bugzilla.redhat.com/show_bug.cgi?id=560774 setroubleshoot_trace_hash:fac7daa743f48e84b0f1adddd13eaffce1b2c8dc6a173b5aef41026d43819c99 Both not marked as dups. One possible problem is if the code does not find white board matches if a bug is closed or closed as a dup.
It's not matching because the 'component' is different. The current dup detection code in report requires both that the hash value matches and the component matches. I intentionally added the requirement that the component match on the grounds that (it seemed to me) problems reported against two different components shouldn't match. In retrospect this was mistaken. I didn't consider the cases where components are changed after the report is filed. Additionally I now realize the hash tag itself will I'll change this back to not comparing component.
(In reply to comment #1) > Additionally I now realize the hash tag itself will ... solve the 'reported against two different components' problem I thought I was solving with this change.
Is report available in F12 yet?
(In reply to comment #3) > Is report available in F12 yet? Yes.
Ok I am going to push the rawhide setroubleshoot package that uses report into Rawhide and then into RHEL6.
(In reply to comment #5) > Ok I am going to push the rawhide setroubleshoot package that uses report into > Rawhide and then into RHEL6. "into" _F-12_ "and then into RHEL6"? Thank you.
Yes that is what I meant.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I fixed this some time ago, but forgot to mark it fixed.
(In reply to comment #9) > I fixed this some time ago, but forgot to mark it fixed. No I didn't. Confused this with other problems.
corrected upstream.
report-0.12-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/report-0.12-1.fc13
report-0.12-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/report-0.12-1.fc12
report-0.12-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/report-0.12-1.fc11
report-0.12-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/report-0.12-1.el5
report-0.12-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update report'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/report-0.12-1.fc13
report-0.12-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update report'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/report-0.12-1.el5
report-0.12-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
report-0.12-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
report-0.12-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
report-0.12-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.