Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1715054 - gitg fails to start throwing symbol lookup error
Summary: gitg fails to start throwing symbol lookup error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gitg
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ignacio Casal Quinteiro (nacho)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-29 13:27 UTC by Julian Sikorski
Modified: 2019-06-07 00:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-07 00:58:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Julian Sikorski 2019-05-29 13:27:20 UTC 
Description of problem:
Attempting to start gitg results in a symbol lookup error

Version-Release number of selected component (if applicable):
3.32.0-1.fc30.x86_64

How reproducible:
always

Steps to Reproduce:
1. update to gitg-3.32.0-1.fc30.x86_64
2. attempt to launch gitg

Actual results:
gitg: symbol lookup error: /lib64/libgitg-1.0.so.0: undefined symbol: ggit_remote_push

Expected results:
gitg starts

Additional info:
Why is error thrown about /lib64/libgitg-1.0.so.0 when gitg-libs installs the files into /usr/lib64/libgitg-1.0.so.0?
Comment 1 Kalev Lember 2019-05-29 13:35:40 UTC 
This should be already fixed by https://src.fedoraproject.org/rpms/gitg/c/e0bbe2377875b3be5569032f082c7cbe4afcad68?branch=master . The update however was unpushed due to a regression in gitg, see https://gitlab.gnome.org/GNOME/gitg/issues/213
Comment 2 Kalev Lember 2019-05-29 13:39:38 UTC 
I submitted the libgit2-glib update that new gitg requires separately now. You can grab it from https://bodhi.fedoraproject.org/updates/FEDORA-2019-7b7b526134
Comment 3 Ankur Sinha (FranciscoD) 2019-05-29 13:48:19 UTC 
Are they the same error, Kalev? This report
Comment 4 Kalev Lember 2019-05-29 13:52:06 UTC 
No. This report here is a dependency version mismatch: gitg requires new libgit2-glib, but the new version isn't in the repos because it got unpush due to the other regression.
Comment 5 Julian Sikorski 2019-05-29 13:55:46 UTC 
I can confirm that libgit2-glib-0.28.0.1-1.fc30.x86_64.rpm fixes the problem. Thanks!
Comment 6 Fedora Update System 2019-05-29 14:06:39 UTC 
FEDORA-2019-7b7b526134 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7b7b526134
Comment 7 Kalev Lember 2019-05-29 14:07:47 UTC 
Great, thanks for testing! I'll went ahead and marked the split out libgit2-glib update as fixing this (it's not the whole story because what's really needed is a gitg build that has versioned requires, but we can't push that out right now because of the other regression).
Comment 8 Fedora Update System 2019-05-30 13:58:06 UTC 
libgit2-glib-0.28.0.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7b7b526134
Comment 9 Fedora Update System 2019-06-07 00:58:24 UTC 
libgit2-glib-0.28.0.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.