Upgrade to gnome-keyring/seahorse 3.4

[Jeremy Bícha]

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

[Jeremy Bícha (jbicha)]

The ubuntu+1 forum testers identified two bugs http://ubuntuforums.org/showthread.php?t=1936161

The second one sounds bad: https://bugzilla.gnome.org/show_bug.cgi?id=671441

[Martin Pitt (pitti)]

I have no objections against packaging gcr, if it does not conflict with existing packages.

gnome-keyring is a very sensitive piece in the stack, and 3.4 got a lot of code an structural changes, so I'm very hesitant to upgrade it at this point. It's used by a lot of programs, not just empathy but also nm-applet, ubuntuone, launchpadlib, etc. So far it was not necessary to update the packages, so we rather kept the known-good one.

Is it realistically possible to patch gnome-shell to run with libgnome-keyring 3.2?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jeremy Bícha (jbicha)]

Ok, the more serious keyring password bug was fixed upstream. I've applied the patch, uploaded the new version to the GNOME 3 PPA, and verified that it works (after logging out and back in).

After almost a week of testing with me calling for testers on Google+ and the Ubuntu+1 forum, there's just one still open bug: https://bugzilla.gnome.org/show_bug.cgi?id=671525 Maybe I should put out a blog post on Planet Ubuntu asking for testing?

Personally, I haven't had any problems with the gnome-keyring stack. I really liked how we were able to ship GNOME Shell in Ubuntu 11.10 without really patching anything and would love for that to be true for 12.04 too.

[Jeremy Bícha (jbicha)]

Rico has a patch for GNOME Shell to revert the gnome-keyring dependency and it continues to work well even against the latest Shell git snapshots. I guess if Ubuntu's not willing to take the risk of the new refactored gnome-keyring after Feature Freeze, we can drop this bug since it's not "needed" any more.

[Jeremy Bícha (jbicha)]

Unsubscribing the Release Team.

[Martin Pitt (pitti)]

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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-keyring - 3.4.1-1ubuntu1

---------------
gnome-keyring (3.4.1-1ubuntu1) quantal; urgency=low

  * Merge with Debian (LP: #947447). Remaining Ubuntu changes:
    - debian/gnome-keyring.gsettings-override:
      Prefer keyserver.ubuntu.com.
    - debian/gnome-keyring.ubiquity:
      Apply capabilities at the end of the ubiquity process to make sure new
      installs have gnome-keyring-daemon with cap_ipc_lock+ep. Install this
      in debian/rules.
    - 04_nodisplay_autostart.patch:
      Clean up Startup Applications dialog by hiding default apps.

gnome-keyring (3.4.1-1) experimental; urgency=low

  [ Jeremy Bicha ]
  * New upstream release.
    - gck and gcr libraries have been split off to separate gcr source
  * debian/control.in: Bump Standards-Version to 3.9.3. No further changes.
  * Drop git patches as they've been applied upstream.
  * Rewrite copyright file using the machine-readable format 1.0.

  [ Jordi Mallach ]
  * New upstream release.
  * Fix some copyright notices in copyright file.
  * Bump Build-Depends.
  * Build-Depend on libselinux1-dev.
  * Bump to debhelper v9.
  * Stop configuring with --enable-static.
 -- Jeremy Bicha <email address hidden> Wed, 16 May 2012 17:39:27 -0400