Hi, I came across this bug while trying to run requestbackport as well...
> This comes from a bad combination of python-crypto and python-keyring > (see http://bugs.debian.org/675379; python-keyring: CryptedFileKeyring > is insecure). python-keyring got fixed already in unstable but didn't > migrate to testing yet. > Someone familiar with the Debian process should check if it's still > possible to let python-keyring migrate to testing. ...but even after installing python-keyring from unstable, requestbackport is still unusable. $ requestbackport supertuxkart Traceback (most recent call last): File "/usr/bin/requestbackport", line 294, in <module> main() File "/usr/bin/requestbackport", line 275, in main Launchpad.login(options.lpinstance) File "/usr/lib/python2.7/dist-packages/ubuntutools/lp/lpapicache.py", line 66, in login version=api_version) File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 539, in login_with credential_save_failed, version) File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 342, in _authorize_token_and_login authorization_engine.unique_consumer_id) File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 282, in load return self.do_load(unique_key) File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 336, in do_load 'launchpadlib', unique_key) File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 37, in get_password return _keyring_backend.get_password(service_name, username) File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 196, in get_password _, session = service_iface.OpenSession("plain", "") File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "OpenSession" with signature "ss" on interface "org.freedesktop.Secret.Service" doesn't exist There isn't a different version of python-crypto in unstable that I can test with. Michael: the reason why python-keyring can't migrate to testing right now is because Debian is in freeze, and updates such as new upstream releases don't comply with the freeze policy [1]. Is there a way to fix this bug with the current version of python-keyring in testing instead? Regards, Vincent [1] http://release.debian.org/wheezy/freeze_policy.html -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
