Bug 26927 - GTG can't find liblarch and liblarch_gtk
Summary: GTG can't find liblarch and liblarch_gtk
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2020-07-10 09:37 CEST by andre salaun
Modified: 2020-08-01 01:27 CEST (History)
5 users (show)

See Also:
Source RPM: gtg-0.3.1-9.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description andre salaun 2020-07-10 09:37:41 CEST 
Install gtg with urpmi :

urpmi gtg
Pour satisfaire les dépendances, les paquetages suivants vont être installés :
  Paquetage                      Version      Révision      Arch    
(média « Core Release (distrib1) »)
  gtg                            0.3.1        9.mga7        noarch  
  liblarch                       3.0          3.mga7        noarch  
un espace additionnel de 10Mo sera utilisé.
3.8Mo de paquets seront récupérés.


launch gtg :
$ gtg
GTG can't find liblarch and liblarch_gtk. To install missing libraries,
run the following command in the current folder:

git clone https://github.com/liblarch/liblarch ../liblarch

More information about liblarch: https://live.gnome.org/liblarch/
[andre@gaia Bureau]$ gtg
GTG can't find liblarch and liblarch_gtk. To install missing libraries,
run the following command in the current folder:

git clone https://github.com/liblarch/liblarch ../liblarch

More information about liblarch: https://live.gnome.org/liblarch/
Comment 1 David GEIGER 2020-07-10 12:13:40 CEST 
Indeed it can't work as liblarch is python3 and gtg is still python2.

So please test upcoming gtg-0.4.0-1.mga7 update in Core/Updates_testing repo!

CC: (none) => geiger.david68210

Comment 2 andre salaun 2020-07-10 15:07:49 CEST 
gtg-0.4.0-1mga7 is ok.
Comment 3 David GEIGER 2020-07-11 06:33:47 CEST 
Assigning to QA,


Advisory:
========================

Our current gtg can't work at all as its code is still on python2 while one of its dependencies liblarch is on python3. So this update fixes this issue porting gtg to the latest upstream release now ported to python3.

========================

Packages in 7/core/updates_testing:
========================
gtg-0.4.0-1.mga7.noarch.rpm

Source RPM: 
========================
gtg-0.4.0-1.mga7.src.rpm

Assignee: bugsquad => qa-bugs

Comment 4 Len Lawrence 2020-07-11 18:47:42 CEST 
mga7, x64

Confirmed the problem and updated gtg.
      1/7: python3-cheetah       
      2/7: python3-configobj     
      3/7: python3-bugzilla      
      4/7: lib64gnome-keyring-gir1.0
      5/7: python3-suds          
      6/7: python3-simplejson    
      7/7: gtg 

$ gtg
2020-07-11 17:40:47,605 - INFO - cleanxml:openxmlfile:176 - No suitable backup was found
2020-07-11 17:40:47,607 - INFO - cleanxml:openxmlfile:176 - No suitable backup was found
2020-07-11 17:40:47,607 - INFO - cleanxml:openxmlfile:176 - No suitable backup was found

The gui launched fine.
Read Getting Started and created a dummy task for today and it appeared at the head of the list.  Edited it to start tomorrow and it dropped to the bottom.

This confirms comment 2.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => tarazed25

Comment 5 Thomas Andrews 2020-07-12 01:37:16 CEST 
Validating. Advisory in Comment 3.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

Dave Hodgins 2020-07-31 12:11:38 CEST

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 6 Mageia Robot 2020-08-01 01:27:27 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0161.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.