Thanks for the update Sebastien! That's very good news for me to hear!

So, I have been using linux for a decade, but I have not been using
Ubuntu nearly so long. What is the "correct" way to test the package
from raring (I assume the next release name) in a mostly quantal system?
Or would I need to upgrade entirely to test the new version of
evolution-indicator?

The way I would have done this in the past is add the raring repository
to my system, install evolution-indicator using apt-get so as to get any
necessary raring dependencies, and then change my repositories back go
quantal (without running a dist-upgrade for sure). Is this still a
reasonable way to approach this way, or is there something more clever
available?

Wonderful work! Now I am much more excited to see 13.04!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1040259

Title:
  FFE: libmessaging-menu transitions for quantal

Status in Gmail Watcher:
  Triaged
Status in Lightread:
  New
Status in Quassel Irc Client:
  New
Status in Skype-wrapper:
  In Progress
Status in “evolution-indicator” package in Ubuntu:
  Triaged
Status in “gm-notify” package in Ubuntu:
  Triaged
Status in “gwibber” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “kdenetwork” package in Ubuntu:
  New
Status in “kdepim” package in Ubuntu:
  New
Status in “libdbusmenu-qt” package in Ubuntu:
  New
Status in “libunity-webapps” package in Ubuntu:
  Fix Released
Status in “liferea” package in Ubuntu:
  Triaged
Status in “pidgin” package in Ubuntu:
  Fix Released
Status in “pidgin-libnotify” package in Ubuntu:
  Fix Released
Status in “quassel” package in Ubuntu:
  New
Status in “smuxi” package in Ubuntu:
  Fix Released
Status in “telepathy-indicator” package in Ubuntu:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  Fix Released
Status in “unity-mail” package in Ubuntu:
  Fix Released
Status in “xchat-indicator” package in Ubuntu:
  Fix Released
Status in “gm-notify” source package in Quantal:
  Triaged
Status in “gwibber” source package in Quantal:
  Fix Released
Status in “indicator-messages” source package in Quantal:
  Fix Released
Status in “kdenetwork” source package in Quantal:
  New
Status in “kdepim” source package in Quantal:
  New
Status in “libdbusmenu-qt” source package in Quantal:
  New
Status in “libunity-webapps” source package in Quantal:
  Fix Released
Status in “liferea” source package in Quantal:
  Triaged
Status in “pidgin” source package in Quantal:
  Confirmed
Status in “pidgin-libnotify” source package in Quantal:
  In Progress
Status in “quassel” source package in Quantal:
  New
Status in “smuxi” source package in Quantal:
  Fix Released
Status in “telepathy-indicator” source package in Quantal:
  Fix Released
Status in “thunderbird” source package in Quantal:
  Fix Released
Status in “unity-mail” source package in Quantal:
  Fix Released
Status in “xchat-indicator” source package in Quantal:
  Fix Released

Bug description:
  indicator-messages got updated, introducing a new libmessaging-menu
  api (deprecating the old libindicate library) which should make
  application developper's life easier.

  The indicator work is done and the library is ready and we started
  porting applications

  The current stack is being tested in https://launchpad.net/~ubuntu-
  desktop/+archive/ppa/

  It includes
  - indicator-messages
  - gwibber
  - indicator-telepathy
  - thunderbird (soon, work is being finished)

  which is what we consider the minimal set for landing the feature

  for quantal we will add those soon:
  - pidgin
  - xchat-indicator
  - evolution-indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to