© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
A possible two-step solution to this problem could be:
1) Fix apport to include a list of apt sources in use (without any credentials as included in sources.list files) in the crash report, so that the server may determine if necessary to pull in dbgsym packages from those PPAs to get a proper retrace.
2) Fix the retracer to add the necessary sources entries to grab additional dbgsym packages from the PPAs, or to flag the error as not retraceable, due to required packages not being installable, as they are from private PPAs, external archives, manually installed, etc…
This could be done initially as a whitelisted set of PPAs to allow installing additional packages from, on the server, so that packages from landing silo PPAs may be used in retracing. I think it would be good to open this up to all public PPAs in the future as well, as long as any security and other concerns are taken care of, and if we could open up viewing of crashes to others via SSO, so that they can see crash reports for packages in PPAs they own (if that is at all viable).