Martin Jambor <mjambor@suse.cz> writes:

On Wed, Apr 10 2024, Michael Pujos wrote:

...

Any request to https://debuginfod.opensuse.org  results in a 503 with a deprecation message. This makes gdb unable to retrieve debuginfo data automatically.

That is a known issue: https://progress.opensuse.org/issues/151594

For various reasons (mostly unknown to me) the service needs to be re-created from scratch. We have already started the work but because of availability of the person leads the effort, it is still going to take at least many weeks if not a few months.

Is it not an option to run the existing service until there's a new or it it incompatible or something similar?

Who is leading the effort? Is there some way to make requests for the new services somewhere, e.g. report feature requests? My request would be to keep debuginfod information for many previous tumbleweed snapshots, at least for all snapshots available here: https://download.opensuse.org/history/ because not everyone always stays completely up to date all the time and debugging crashes that happened weeks ago should still be possible. Off-topic but anyway: why are there so few past snapshots kept in the history archives? Would be great if the number could be increased to at least cover the last 2 months, or is there such a big problem with disk space?

Dear Bernhard, Thanks for your reply, I am aware of your longer history archive and it already helped me a lot. While everyone who knows about your effort can surely profit from it, I would find it great if this could become something official, or at least documented in the wiki, or are there bandwidth concerns? As for debuginfod: I know the underlying debug symbol packages are all in the archive anyway, however this is still unpractical, manually chasing missing symbols is really a pain, especially for more complex packages. It is simply such a pleasure to just let gdb fetch all the info required automatically and this actually leads to me reporting crashes with good backtraces upstream, while I often do not find time to manually chase debug packages on my productivity system. Other distributions have / had their own solutions to make reporting good crash reports practical, e.g. Fedora has abrt, which also has a utility for automatic debug symbol fetching, Ubuntu has apport which is similar. I did not really care about Opensuse not having anything comparable since the advent of debuginfod, but I thought since you need to rebuild the service anyway, it is a good time to discuss about improvements. While the previous debuginfod service for Opensuse worked well in most of the cases, it is still a limitation that one can not really debug older crashes well (like a crash I had 5 weeks ago that I did not have time to look into yet). Isn't it the case anyway that debuginfod just indexes existing debuginfo packages? Would it be possible to keep a reasonable history of indexed snapshots, so that gdb can generate full backtraces automatically even for older dumps? Thanks very much! On 4/25/24 17:47, Bernhard M. Wiedemann wrote:

On 23/04/2024 21.02, Esokrarkose@gmail.com wrote:

...

Who is leading the effort? Is there some way to make requests for the new services somewhere, e.g. report feature requests? My request would be to keep debuginfod information for many previous tumbleweed snapshots, at least for all snapshots available here: https://download.opensuse.org/history/ because not everyone always stays completely up to date all the time and debugging crashes that happened weeks ago should still be possible. Off-topic but anyway: why are there so few past snapshots kept in the history archives? Would be great if the number could be increased to at least cover the last 2 months, or is there such a big problem with disk space?

I keep a longer history of 4 years at https://opensuse.zq1.de/history/ and it takes around 11 TB so far. Older files are on a low-bandwidth link, though.