Control: severity -1 serious On 2013-06-29 15:38:29, Dmitry Shachnev wrote: > > Package: python-keyring > Version: 1.4-1 > Severity: important > Tags: pending upstream > Control: forwarded -1 https://bitbucket.org/birkenfeld/sphinx/issue/1175 > > There is a chance that after upgrading python-keyring to 1.4, the GNOME > Keyring backend > becomes default instead of the SecretService one, or the default backend will > switch > from time to time. > > As GNOME Keyring backend currently is not able to read passwords stored using > SecretService backend, an user will sometimes have to re-set their passwords, > which is > not optimal. > > I have proposed a pull request upstream that makes GNOME Keyring use the same > password > attributes as the SecretService backend does (old attributes are supported for > compatibility), and backported it as a distro patch in the SVN repository.
I'm raising the severity to serious to stop it from entering testing. I'd like to wait until upstream has commented on the patch as I don't want to carry a patch that is incompatible with the rest of the world. So an upload fixing this bug is just waiting on a word from upstream. Regards -- Sebastian Ramacher
signature.asc
Description: Digital signature
