GTG

put liblarch out of the repository

Bug #827961 reported by Lionel Dricot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTG
Fix Released
High
Unassigned

Bug Description

it requires separate packaging

Related branches

Changed in gtg:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Lionel Dricot (ploum)
milestone: none → 0.2.9
Changed in gtg:
milestone: 0.2.9 → 0.3
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Currently working on it. Should it be in the 0.2.9 or should we wait 0.3 ?

Changed in gtg:
status: Confirmed → In Progress
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

The bug is now considered fixed in the linked branch.

It goes like this:

1) GTG tries to import liblarch from the system.
2) if it fails, GTG tries to import liblarch from the parent folder.
3) if it fails, it tells you the git command to run to put liblarch in the parent folder

It also checks if the API version of liblarch is compatible.

Izidor Matušov (izidor)
Changed in gtg:
milestone: 0.3 → 0.2.9
status: In Progress → Fix Committed
Izidor Matušov (izidor)
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.