People file the bugs in different ways, under pacman, under gcc etc. It creates a lot of noise and most gcc-related bug reports don't concern your issue.
Have you searched the forums before filing the bug report? The issue is not new, even if the version numbers changed:
* https://bbs.archlinux.org/viewtopic.php?pid=1062705
* https://bbs.archlinux.org/viewtopic.php?pid=1057709
* https://bbs.archlinux.org/viewtopic.php?id=139103
You can solve it the same way as https://bbs.archlinux.org/viewtopic.php?id=135702
I admit it's not clear if it's the same issue or not. If the developer treats all such reports as duplicates of https://bugs.archlinux.org/task/27214 w/o explicitly stating this, it can easily turn into guesswork on part of the submitter.
Sorry, I don't see how your message is related to my issue. The issue was: bug-tracker search engine doesn't treat '-' char as delimiter. As a result, the engine doesn't show 'gcc-libs'-containing items when 'gcc' search context is using. At the moment of opening that issue there were not any similar issues with 'gcc' context (again, 'gcc' rather 'gcc-libs').
]]>bugt ()
{
$BROWSER "https://bugs.archlinux.org/index/proj0?string=$*&project=0&search_name=&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index&order=id&sort=desc"
}
I type
bugt gcc-libs
and get a list of bug reports (including the closed ones) sorted by ID, descending.
]]>Sorting them by date or ID obviously helps in quickly spotting recent similar issues.
]]>So what is that robust way to search tasks to avoid duplicates?
]]>