Yes and no. Right, I could press two buttons and reopen ticket. No, I am not a reporter so there would be no actual result in it. If you digg into closed/dublicate reports you will see that there were some communication in them. But it stopped every time that bug been marked as dublicate. Reportes of that bugs as I think suggest that if it is a dublicate someone for sure is working on it. And it is wrong. Reporter of first bugreport just foggot already he made it. So. First bugreport has reporter why does not wont to help (what is rather often with abrt generated reports). Reporters of dublicates think that first bug is under revision and stop working on their reports (who will blame them? there reports are closed). All became into CLOSED status after F16 EOL, nothing became better. > Then the original one could be reopened and version set to F18. > > "If you can reproduce this bug against a currently maintained version of > Fedora please feel free to reopen this bug against that version." > > It would be probably possible to check all dupes automatically but > again a corner case, fixable manually (if somebody takes care). > > Btw. as asked frequently in the previous EOL thread and to make it > easier for me and upcoming guys responsible for EOL - the script is > now available in the GIT of Fedora Project Schedule hosted project [1]. > > Jaroslav > > [1] https://fedorahosted.org/fedora-project-schedule/ > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
