See the instructions for distro packagers at https://invent.kde.org/plasma/drkonqi/-/blob/master/README.md
Metadata Update from @siosm: - Issue set to the milestone: Plasma 5.25 - Issue tagged with: experience, packaging
Looks like this was the part missing from https://pagure.io/fedora-kde/SIG/issue/217 :)
If I install gdb.minimal and make a symlink to it in /usr/local/bin/gdb then I get working backtrace in DrKonqi.
/usr/local/bin/gdb
I've filed https://bugs.kde.org/show_bug.cgi?id=461434 and I'll add gdb.minimal to Kinoite, maybe with a temporary symlink until this is resolved.
Metadata Update from @siosm: - Issue assigned to siosm
Metadata Update from @siosm: - Issue set to the milestone: Plasma 5.26 (was: Plasma 5.25)
Metadata Update from @siosm: - Issue tagged with: kinoite
Metadata Update from @siosm: - Issue set to the milestone: Plasma 5.27 (was: Plasma 5.26)
Metadata Update from @siosm: - Issue marked as blocking: #112
Metadata Update from @siosm: - Issue set to the milestone: Future Release (was: Plasma 5.27)
https://pagure.io/workstation-ostree-config/pull-request/394
Instead of local symlinks, we can use a functionality in RPM to strip a suffix from a command line utility when it's installed. Example in curl: https://src.fedoraproject.org/rpms/curl/blob/rawhide/f/curl.spec#_172-177 (https://rpm-software-management.github.io/rpm/manual/spec.html)
If this does not work, another option is to exclude the recommended dependency from https://kojipkgs.fedoraproject.org//work/tasks/5857/102885857/root.log
https://src.fedoraproject.org/rpms/gdb/pull-request/90
New PR as I found another way: https://pagure.io/workstation-ostree-config/pull-request/396
The gdb-minimal fix might be useful in the future but we don't strictly need it now.
Metadata Update from @siosm: - Issue set to the milestone: Fedora Linux 39 (was: Future Release)
Metadata Update from @siosm: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Oops no idea how I reopened this. Closing
Metadata Update from @farchord: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I haven't even touched this I don't know why it keeps opening. Might be because it's in the in-progress section but it was closed?
Log in to comment on this ticket.