Releases retrieved: 0.4.0 Upstream release that is considered latest: 0.4.0 Current version/release in rawhide: 0.3.9-1.fc38 URL: https://pwmt.org/projects/girara/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/6750/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/girara
This includes quite an important bugfix, so we should update whatever releases are appropriate. https://git.pwmt.org/pwmt/girara/-/commits/0.4.0 To reproduce: - open a file with an index in zathura - hit "tab" to see the index - see segfault I got a stack trace (attaching) and checked to see if it was reported, and it seems fixed in https://git.pwmt.org/pwmt/girara/-/commit/6926cc1234853ccf3010a1e2625aafcf462ed60e Cheers, Ankur
Created attachment 1952774 [details] segfault backtrace
Zathura still says > 0.3.7, so we shouldn't need a rebuild of all deps.
Hi all I do not plan to work on this update before next week... So, if one of you is quicker than me, feel free to update girara.
If I understand upstream correctly, this will hit us with glib2 2.76 which is in F38 and up but not slated for F37. OTOH, the difference between girara 0.3.9 and 0.4.0 is basically one commit which avoids the glib2 problem by storing a value before before glib2 2.76 releases the struct member which earlier glib2 did not, so the fix is neither necessary on F37, nor will it make any difference. So I guess we can just leave F37 as is and note that we can pull it up when needed, or do it now to prepared just in case.
We should update F38 ASAP at least, so that when folks install/upgrade they get the updated version. We can sync F37 etc. later if there's another zathura update that requires updating the stack?
PR: https://src.fedoraproject.org/rpms/girara/pull-request/3
FEDORA-2023-5a61ee26dc has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5a61ee26dc
FEDORA-2023-5a61ee26dc has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5a61ee26dc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5a61ee26dc has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.