Description of problem: When abrt finds a bug already reported, but the existing report is closed with WONT_FIX because of EOL, it will not open a new report. Version-Release number of selected component (if applicable): abrt-2.0.18-1.fc17.i686 How reproducible: always Steps to Reproduce: 1. Get a core dump reported for an EOL version, e.g. bug#720467 2. abrt won't open a bug for current fedora version 3. Actual results: No way to reopen bug for new Fedora version. Expected results: Some way to reopen bug for new Fedora version using abrt - maybe as simple as submitting collected info to a manually entered bug#. Additional info:
If creating a new bug will be automatic, abrt only needs to know whether its own Fedora version is EOL. That can be a static configuration supplied as part of the RPM. Then, the logic should be: if the existing bug is for an EOL Fedora, and Fedora of abrt is not EOL, then ignore the existing bug.
Come to think of it, some RPM already has the EOL configured, because I get a notifier from Gnome after EOL advising me to upgrade.
Thank you for the bug report. This particular bug has already been reported, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 863667 ***