On 09. 12. 20, 11:24, Martin Liška wrote:
We only index Tumbleweed packages for x86_64.
I understood that. But for how long/how many releases you/them keep the debuginfos in place?
Right now, it only indexes are RPMs that we provide by our package servers.
If you have a crash dump, you are out of luck then. The same with coredumpctl, it won't be able to download the debuginfos too. So one still has to have the debuginfo packages installed :(. I am talking about not so often crashes/bugs. You upgrade, run TW for a week and "it" crashes finally again. You need the corresponding debuginfo, but debuginfo is gone from the server by that time already. People barely upgrade to every TW release.
TW is problematic as one can't even install a version of a package that is one month old.
One sometimes has month old installed packages though :). $ uptime 11:35:34 up 30 days 3:40, 19 users, load average: 0.78, 1.00, 1.08
So unfortunately, one needs to first update a TW system in order to have it working.
That won't work well. It works only for reproducible crashes (you upgrade and trigger the crash). For more usual cases, we would need at least a week old debuginfos.
If they dismiss with every TW release, it's quite pointless. If they are kept around for a month, it makes a lot of sense.
Yes, it's not supported right now.
So any plans on this then :)? thanks, -- js suse labs