libunity

libunity-tool doesn't parse scope files correctly

Bug #1235342 reported by Michal Hruby
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libunity
Fix Released
Low
Michal Hruby
libunity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Scope files that are using current GroupName and DBusName in their .scope files do not work with libunity-tool as it doesn't use the protocol library.

Related branches

lp:~mhr3/libunity/fix-1235342
PS Jenkins bot (community): Approve (continuous-integration)
Paweł Stołowski (community): Approve
Diff: 29 lines (+12/-5)
1 file modified
tools/unity-tool.vala (+12/-5)
Michal Hruby (mhr3)
Changed in libunity:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Michal Hruby (mhr3)
status: Confirmed → In Progress
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:libunity at revision 301, scheduled for release in libunity, milestone 7.0.0

Changed in libunity:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libunity - 7.1.2+13.10.20131010-0ubuntu1

---------------
libunity (7.1.2+13.10.20131010-0ubuntu1) saucy; urgency=low

  [ Michal Hruby ]
  * libunity-tool: Use protocol library to get scope information. (LP:
    #1235342)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 301
 -- Ubuntu daily release <email address hidden> Thu, 10 Oct 2013 00:08:05 +0000

Changed in libunity (Ubuntu):
status: New → Fix Released
Michal Hruby (mhr3)
Changed in libunity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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