Hi Kevin, thanks for your reply. I am guessing one factor against easy linking to source is how its archived in the source control Lookaside Cache. Just for kicks I threw together a small proof of concept RPM content browser web service. It pulls the packages on-demand, and works surprisingly well. The debuginfo RPM contents seem like ideal targets to surface for stack traces, as they have a nice 1:1 relationship with binaries. https://github.com/jwmullally/test_rpmbrowser/blob/master/README.md http://rpmbrowser-jwmullally.rhcloud.com/ https://retrace.fedoraproject.org/faf/problems/1354441/ http://rpmbrowser-jwmullally.rhcloud.com/rpm/nautilus-debuginfo-3.18.1-1.fc23.x86_64.rpm/browse/usr/src/debug/nautilus-3.18.1/libnautilus-private/nautilus-progress-info.c?hl_lines=96#LINE-96 I'll probably take that site down in a few weeks. SRPM extraction doesn't work due to "rpm" not being executable on the old OpenShift containers. It gets the RPMs from http://kojipkgs.fedoraproject.org , if that is an issue let me know, but I couldn't see a quick way of using mirrors without having to do index lookups. - Joe _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
