Bug#697213: python-keyring: CryptedFileKeyring always forces keyring initalization

2013-01-06 Thread Sebastian Ramacher
Control: severity -1 important Control: retitle -1 python-keyring: CryptedFileKeyring: incomplete migration, broken unlock logic On 2013-01-03 02:15:09, Sebastian Ramacher wrote: > While preparing a tpu upload for the CVEs and testing the migration code, I > came to the conclusion that without th

Bug#697212: Bug#697213: python-keyring: CryptedFileKeyring always forces keyring initalization

2013-01-02 Thread Sebastian Ramacher
On 2013-01-03 00:17:43, Sebastian Ramacher wrote: > … I'm sorry. That mail went to the wrong bug. -- Sebastian Ramacher signature.asc Description: Digital signature

Bug#697213: [sramac...@debian.org: Re: Bug#697213: python-keyring: CryptedFileKeyring always forces keyring initalization]

2013-01-02 Thread Sebastian Ramacher
This mail went to the wrong bug. Forwarding. - Forwarded message from Sebastian Ramacher - Date: Thu, 3 Jan 2013 00:17:43 +0100 From: Sebastian Ramacher To: 697...@bugs.debian.org, Carl Chenet Subject: Re: Bug#697213: python-keyring: CryptedFileKeyring always forces keyring

Bug#697212: Bug#697213: python-keyring: CryptedFileKeyring always forces keyring initalization

2013-01-02 Thread Sebastian Ramacher
Hi Carl, On 2013-01-02 18:46:20, Sebastian Ramacher wrote: > please backport the patch from [1]. Without the patch CryptedFileKeyring > always reinitializes the keyring. While preparing a tpu upload for the CVEs and testing the migration code, I came to the conclusion that without this patch is r

Bug#697213: python-keyring: CryptedFileKeyring always forces keyring initalization

2013-01-02 Thread Sebastian Ramacher
Package: python-keyring Version: 0.9.2-1 Severity: normal Tags: patch upstream fixed-upstream Hi, please backport the patch from [1]. Without the patch CryptedFileKeyring always reinitializes the keyring. Regards [1] https://bitbucket.org/kang/python-keyring-lib/commits/8881c7d88dffc598944c95e