See also bug 1126360. The fix for that bug has resulted in different behavior on Ubuntu and Debian.
workrave fails to build currently in yakkety because in Debian the indicator is stored in /usr/lib/*/indicators3/7/libworkrave.so but in Yakkety, it's: /usr/lib/indicators3/7/libworkrave.so https://launchpad.net/ubuntu/+source/workrave/1.10.15-1/+build/9731661 So please either fix Debian's libindicator or Ubuntu's so that they have the same behavior. Personally, I prefer the multiarch directory. ** Also affects: workrave (Ubuntu) Importance: Undecided Status: New ** Changed in: workrave (Ubuntu) Importance: Undecided => High ** Changed in: workrave (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1126385 Title: Migrate to mulitarch indicators Status in libindicator: Confirmed Status in Unity: Confirmed Status in libindicator package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Status in workrave package in Ubuntu: Triaged Bug description: Currently, the indicators are all non-multiarch for historical reasons. We should enable multiarch indicators. 1) Add a new variable to the libindicator .pc files called something like genericindicatordir which continues to be just /usr/lib 2) Switch the indicatordir variable to a multiarch location (again -- we reverted away from that for bug 1126360) 3) Have unity fallback to look in the genericindicatordir as well as the (now-) multiarch indicatordir for plugins 4) As each indicator gets rebuilt, it will automatically migrate to multiarch, since "indicatordir" is now multiarch. But old indicators will still work. To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/1126385/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp