On Sun, 2017-12-31 at 16:34 +0000, Richard W.M. Jones wrote: > On Sat, Dec 30, 2017 at 03:59:13PM -0800, Adam Williamson wrote: > > When it thinks this, it defaults to a mode where it wants to make > > anything submitted to Bugzilla private, and it seems that in this mode, > > even when it knows a report is a dupe, it won't just add a comment to > > the parent bug, allegedly because it can't make a comment sufficiently > > private (I'm not sure on the details of that particular wrinkle). > > The new bugs are private to ‘fedora_contrib_private’, but ... > > > Instead it files a new private bug and immediately closes it as a > > duplicate of the original bug. You can change this - there's a checkbox > > during the report workflow which decides the behaviour, when abrt > > thinks the report contains sensitive data it defaults to being checked, > > and you can uncheck it if you know it's a false positive - but of > > course most reporters don't bother with this. > > .. I don't believe it's closing these as duplicates, so maybe > it's not this? Sounds like it's not, then, indeed - in the cases I'd seen, the new bugs immediately got closed as dupes. So it's probably a case of it not correctly detecting duplicates. I usually file those here: https://github.com/abrt/satyr -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
