Should install shell-facing plugins in plugin path from libunity-api-dev

Bug #1256011 reported by Michał Sawicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-mir
Triaged
Medium
Gerry Boland
qtubuntu (Ubuntu)
Triaged
Medium
Unassigned
unity-mir (Ubuntu)
Triaged
Medium
Unassigned
unity-notifications (Ubuntu)
Fix Released
Low
Mirco Müller

Bug Description

libunity-api-dev provides a pluginpath now, all shell-specific plugins should be installed under there:

http://bazaar.launchpad.net/~unity-team/unity-api/trunk/revision/112

Example integration:

http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/554/CMakeLists.txt

unity-mir is special in that it might want to suffix it with mir/ or something, so that we can prepend that path when under Mir.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libunity-mir1 0.1+14.04.20131119-0ubuntu2
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.7-0ubuntu1
Architecture: armhf
Date: Thu Nov 28 15:53:14 2013
InstallationDate: Installed on 2013-11-27 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131127.1)
SourcePackage: unity-mir
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Michał Sawicz (saviq) wrote :
Changed in unity-mir (Ubuntu):
status: New → Confirmed
Changed in qtubuntu (Ubuntu):
status: New → Confirmed
Changed in unity-notifications (Ubuntu):
status: New → Confirmed
summary: - Should install the applications plugin in plugin path from libunity-api-
- dev
+ Should install shell-facing plugins in plugin path from libunity-api-dev
Gerry Boland (gerboland)
Changed in unity-mir:
importance: Undecided → Medium
assignee: nobody → Gerry Boland (gerboland)
status: New → Confirmed
status: Confirmed → Triaged
Mirco Müller (macslow)
Changed in unity-notifications (Ubuntu):
assignee: nobody → Mirco Müller (macslow)
Mirco Müller (macslow)
Changed in unity-notifications (Ubuntu):
status: Confirmed → In Progress
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-notifications - 0.1.1+14.04.20140129-0ubuntu1

---------------
unity-notifications (0.1.1+14.04.20140129-0ubuntu1) trusty; urgency=low

  [ Michał Sawicz ]
  * Flush trunk through Train CI.

  [ Albert Astals ]
  * Use QCOMPARE instead of QVERIFY Because it is what we want to do and
    also because it gives us much better failure messages when tests
    fail.

  [ Mirco Müller ]
  * Fixes bug #1200569. (LP: #1200569)
  * Added reporting-support for x-canonical-private-fullscreen hint.
  * Don't use the fullscreen-hint. Fullscreen is meant to be implicitly
    used only by the pinpad-notification.
  * Use new plugin-path provided by pkgconfig of libunity-api-dev, thus
    fixing LP #1256011. (LP: #1256011)
  * Make notification unit-test Q-ified in order to allow nicer ouput in
    case of failures.
  * Change the order of visually stacked snap-decisions to comply with
    the Design-spec for UbuntuTouch notifications. Also updated test to
    verify the new required behaviour.
 -- Ubuntu daily release <email address hidden> Wed, 29 Jan 2014 17:34:33 +0000

Changed in unity-notifications (Ubuntu):
status: In Progress → Fix Released
Changed in unity-mir (Ubuntu):
importance: Undecided → Medium
Changed in qtubuntu (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in unity-mir (Ubuntu):
status: Confirmed → Triaged
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.