desktopcouch keychain access gives useless application name

Also at https://edge.launchpad.net/desktopcouch/trunk/0.4.6 .

Use this diff instead, as it updates no PO or build/ files.

New release that fixes this and other bugs at:

https://edge.launchpad.net/~cmiller/+archive/u1/+sourcepub/777766/+listing-archive-extra

desktopcouch (0.5-0ubuntu1) karmic; urgency=low

  * New upstream release.
    + Fix remote-db-listing bug for SSL/HTTPS services. (LP: #458540)
    + Fix OAuth signatures for SSL urls.
    + Avoid couchdb bug where users' PID files are incorrectly interpreted as
      valid by couchdb, and so after slightly different boot, desktopcouch can
      never start couchdb, causing desktopcouch to quit. (LP: #442120)
    + For dbus, do not resolve data for events signaling a service disappears,
      and use explicit veriable-passing / references. (LP: #440072)
    + Flip push/pull logic in replication information.
    + When pulling from remote DB, do not try to access remote management DB.
    + Use meaningful names for keyring access. (LP: #451333)

 -- Chad MILLER < <email address hidden>> Thu, 22 Oct 2009 17:15:57 -0400

diff.gz, tarball, and .dsc file can be found in chad's ppa at https://edge.launchpad.net/~cmiller/+archive/u1/+sourcepub/777766/+listing-archive-extra

local testing doesn't reveal any obvious problems but I haven't actually witnessed it replicate. But no crashes, perhaps it is waiting for u1 to finish syncing down my files.

Just a cosmetical bug, not a release blocker; removing milestone.

This bug was fixed in the package desktopcouch - 0.5-0ubuntu1

---------------
desktopcouch (0.5-0ubuntu1) karmic; urgency=low

  * New upstream release.
    + Fix remote-db-listing bug for SSL/HTTPS services. (LP: #458540)
    + Fix OAuth signatures for SSL urls.
    + Avoid couchdb bug where users' PID files are incorrectly interpreted as
      valid by couchdb, and so after slightly different boot, desktopcouch can
      never start couchdb, causing desktopcouch to quit. (LP: #442120)
    + For dbus, do not resolve data for events signaling a service disappears,
      and use explicit veriable-passing / references. (LP: #440072)
    + Flip push/pull logic in replication information.
    + When pulling from remote DB, do not try to access remote management DB.
    + Use meaningful names for keyring access. (LP: #451333)

 -- Chad MILLER <email address hidden> Thu, 22 Oct 2009 17:15:57 -0400