Dne 05. 10. 20 v 17:20 Frank Ch. Eigler napsal(a): > The problem is that Fedora itself doesn't run a server, and our test > server can afford to carry only a subset of debuginfo/debugsource rpms > & architectures. So, fedora developers / users cannot get at all the > info, or from an official source. I wonder if it's time to get one > set up. If there is interest, I'd be happy to start discussing > logistics with fedora infrastructure folks. As many pointed ABRT does that. For any crash catched by ABRT you can run: abrt debuginfo-install $ID # id can be taken from `abrt list` The server retrace.fedoraproject.org contains all required packages. I will be more than happy to host there some service which will provide the debuginfod service. But it must be integrated with current ABRT Analytics and Retrace-server so we do not host packages twice. The abrt hangs on #abrt on Freenode. And the upstream is on: https://github.com/abrt/ The playbook for retrace setup is in: https://pagure.io/fedora-infra/ansible/blob/master/f/playbooks/groups/retrace.yml Contribution is more than welcome. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
