How intrusive/safe is that gnome-shell patch to work with g-k 3.2? If
that's reasonable to keep for Precise, I'm leaning towards keeping 3.2
for precise.

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

Title:
  Upgrade to gnome-keyring/seahorse 3.4

Status in “gnome-keyring” package in Ubuntu:
  Confirmed

Bug description:
  The latest gcr is required for gnome-shell 3.4. gcr is a NEW package,
  having been split off from gnome-keyring at the beginning of this
  release cycle. Seahorse has received a major UI overhaul. There's a
  few screenshots of Seahorse at http://iloveubuntu.net/seahorse-335
  -released-new-interface

  I've pushed these packages to the GNOME3 PPA and have been running
  them since Saturday and haven't seen problems yet. Empathy seemed to
  work fine without needing a rebuild.

  http://git.gnome.org/browse/gcr/tree/NEWS
  http://git.gnome.org/browse/gnome-keyring/tree/NEWS
  http://git.gnome.org/browse/seahorse/tree/NEWS

  Reverse-Depends for libgcr and libgck
  ===============
  * empathy
  * gnome-keyring
  * nautilus-sendto-empathy
  * seahorse

  Build logs
  =======
  gcr
    https://launchpad.net/~jbicha/+archive/dev/+build/3257085
  gnome-keyring
    https://launchpad.net/~gnome3-team/+archive/gnome3/+build/3270360
  seahorse
    https://launchpad.net/~jbicha/+archive/dev/+build/3257427

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/947447/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to