lp://staging/ubuntu/lucid-updates/libgnome-keyring

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

12. By Sebastien Bacher on 2010-06-22

* New upstream version
* debian/patches/90_git_is_available_crash.patch:
  - git change to fix a crasher in gnome_keyring_is_available()
    (lp: #530760)
* debian/patches/02_workaround_cpu_use.patch:
  - dropped, the change is in the new version

11. By Sebastien Bacher on 2010-04-15

* debian/patches/02_workaround_cpu_use.patch:
  - use official upstream git version
* debian/patches/01_upstream_gvfsd_cpu_use.patch:
  - dropped this workaround it was not the right change

10. By Sebastien Bacher on 2010-04-01

* debian/patches/02_workaround_cpu_use.patch:
  - change from https://bugzilla.gnome.org/show_bug.cgi?id=606902
    to try to workaround extra cpu use issues (lp: #530605)

9. By Sebastien Bacher on 2010-04-01

Clean the diff.gz again to not revert upstream changes (lp: #532446)

8. By Sebastien Bacher on 2010-03-31

New upstream version

7. By Sebastien Bacher on 2010-03-29

* debian/patches/01_upstream_gvfsd_cpu_use.patch:
  - upstream change which could be solving the gvfsd eating cpu issue
    (lp: #530605)

6. By Sebastien Bacher on 2010-03-23

Correctly use the new version rather than reverting changes in the diff.gz
really close the issues on lp: #526556, #532446 now

5. By Sebastien Bacher on 2010-03-22

* New git version:
  - "Try to return GNOME_KEYRING_ALREADY_EXISTS where possible."
     which fixes gajim creating a keyring at every run (lp: #526556)
  - "Hold reference to operation while waiting for prompt result."
    which fixes empathy failing to access accounts when unlocking the keyring
    (lp: #532446)
* debian/patches/06_ftbfs-armel.patch:
  - the change is in the new version

4. By Alexander Sack on 2010-03-07

* debian/patches/06_ftbfs-armel.patch:
  + fix LP: #533998 - ftbfs on armel; we drop g_asserts on va_list
    types; the macros should be safe on their own

3. By Sebastien Bacher on 2010-02-24

* New git snapshot:
  - "When no default keyring exists, and creating an item, and the default
     keyring was the desired keyring for the item, prompt to create a new
     "default keyring." (lp: #525542)