Hide Forgot
Description of problem: Every single package ever build in fedora is available in koji, abrt should look there instead of complaining it can not find some debuginfos If there is a need to disambiguate koji-built packages from third party packages just request a specific metadata bit in Fedora packages and have koji add it automatically at build time This single change would increase abrt reliability by several orders of magnitude (and reduce developper and tester load) Version-Release number of selected component (if applicable): gnome-abrt-0.3.1-1.fc21.x86_64
(In reply to Nicolas Mailhot from comment #0) > Description of problem: > > Every single package ever build in fedora is available in koji, abrt should > look there instead of complaining it can not find some debuginfos Not directly related to the problem, but this is a wrong assumption. Builds get deleted from koji. > If there is a need to disambiguate koji-built packages from third party > packages just request a specific metadata bit in Fedora packages and have > koji add it automatically at build time I believe a Fedora "watermark" already exists. > This single change would increase abrt reliability by several orders of > magnitude (and reduce developper and tester load) I don't agree. It will increase ABRT's success rate, but the overall effect would be hardly noticeable - the majority of people are using remote analysis (Retrace Server). There are also several non-trivial problems. First, the debuginfo packages are searched by build-ids, koji does not provide a way to do this - see #1008928. Second, in local analysis, even if you have the correct debuginfo, you need the matching binary, which does not necessarily need to be present on your system. Third, this solution does not scale. The current implementation looks for debuginfo packages in mirrored repositories, while querying koji from all around the world might result into DoS (okay, maybe paranoia).
(In reply to Michal Toman from comment #1) > (In reply to Nicolas Mailhot from comment #0) > > Description of problem: > > > > Every single package ever build in fedora is available in koji, abrt should > > look there instead of complaining it can not find some debuginfos > Not directly related to the problem, but this is a wrong assumption. Builds > get deleted from koji. Not on the timescales abrt is usually run > > If there is a need to disambiguate koji-built packages from third party > > packages just request a specific metadata bit in Fedora packages and have > > koji add it automatically at build time > I believe a Fedora "watermark" already exists. > > > This single change would increase abrt reliability by several orders of > > magnitude (and reduce developper and tester load) > I don't agree. It will increase ABRT's success rate, but the overall effect > would be hardly noticeable - the majority of people are using remote > analysis (Retrace Server). retrace should also fall back on koji unless of complaining it does not know a package version > There are also several non-trivial problems. First, the debuginfo packages > are searched by build-ids, koji does not provide a way to do this - see > #1008928. abrt knows the dso names, the rpm and srpm who provides them, and approximate version at time of crash. This is enough to make pretty accurate guesses (I have to do it all the time manually to get good traces) > Second, in local analysis, even if you have the correct debuginfo, > you need the matching binary, which does not necessarily need to be present > on your system. Likewise, it is available in koji for Fedora packages > Third, this solution does not scale. The current > implementation looks for debuginfo packages in mirrored repositories, while > querying koji from all around the world might result into DoS (okay, maybe > paranoia). won't DoS more than asking users to download random packages from koji because he abrt trace can not be used. Won't DoS at all if it's used as fallback for the bits that can not be satisfied from current repos. Will actually provide data to the people who manage repositories on the correct debuginfo retention strategies in official repos to satisfy abrt needs
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.