Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
Cloud:OpenStack:Liberty
python-keyring
python-keyring.changes
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File python-keyring.changes of Package python-keyring
------------------------------------------------------------------- Thu Dec 17 12:59:08 UTC 2015 - dmueller@suse.com - drop keyring-import-gi.patch, and update keyring-gnome-3.18.patch, which introduces the regression ------------------------------------------------------------------- Mon Sep 17 11:41:56 UTC 2015 - m0ses@samaxi.de - Added keyring-import-gi.patch: gi.require_version is called and not found if gi is not imported ------------------------------------------------------------------- Mon Sep 7 08:40:56 UTC 2015 - dimstar@opensuse.org - Update to version 5.4: + Prefer setuptools_scm to hgtools. - Replace python-hgtools BuildRequires with python-setuptools_scm, following upstreams change back to setuptools_scm. - Add keyring-gnome-3.18.patch: Silence a warning: on GNOME 3.18, it is mandatory to specify the version to be imported. ------------------------------------------------------------------- Tue Apr 28 11:06:12 UTC 2015 - mimi.vx@gmail.com - update to version 5.3 + changed licence to Python-2.0 and MIT * Prefer setuptools_scm to hgtools. * Version numbering is now derived from the code repository tags via hgtools. * Build and install now requires setuptools. * The entry point group must look like a module name, so the group is now “keyring.backends”. * Added preliminary support for loading keyring backends through setuptools entry points, specifically “keyring backends”. ------------------------------------------------------------------- Tue Nov 11 17:45:50 UTC 2014 - i@marguerite.su - use update-alternatives for /usr/bin/keyring because there'll be a python3-keyring package ------------------------------------------------------------------- Tue Oct 14 09:57:54 UTC 2014 - kgronlund@suse.com - Update to version 4.0 (boo#901066): * Removed ``keyring_path`` parameter from ``load_keyring``. See release notes for 3.0.3 for more details. * Issue #22: Removed support for loading the config from the current directory. The config file must now be located in the platform-specific config location. - Changes from version 3.7: * Issue #22: Deprecated loading of config from current directory. Support for loading the config in this manner will be removed in a future version. * Issue #131: Keyring now will prefer ``pywin32-ctypes <https://pypi.python.org/pypi/pywin32-ctypes>``_ to pywin32 if available. - Changes from version 3.6: * Gnome keyring no longer relies on the GNOME_KEYRING_CONTROL environment variable. * Issue #140: Restore compatibility for older versions of PyWin32. - Switch to pytest since nose doesn't support test fixtures and fails: - Add BuildRequires: python-pytest - Remove BuildRequires: python-nose ------------------------------------------------------------------- Thu Aug 28 13:05:31 UTC 2014 - dmueller@suse.com - reduce/fix build requires ------------------------------------------------------------------- Mon Mar 17 10:12:00 UTC 2014 - speilicke@suse.com - Update to version 3.6: * Add support for packages that wish to bundle keyring by using relative imports throughout. - Changes from version 3.5: * Issue #49: Give the backend priorities a 1.5 multiplier bump when an XDG_CURRENT_DESKTOP environment variable matches the keyring's target environment. * Issue #99: Clarified documentation on location of config and data files. Prepared the code base to treat the two differently on Unix-based systems. For now, the behavior is unchanged. - Changes from version 3.4: * Extracted FileBacked and Encrypted base classes. * Add a pyinstaller hook to expose backend modules. Ref #124 * Pull request #41: Use errno module instead of hardcoding error codes. * SecretService backend: correctly handle cases when user dismissed the collection creation or unlock prompt. ------------------------------------------------------------------- Sun Dec 8 18:49:56 UTC 2013 - p.drouand@gmail.com - Update to version 3.3 * KWallet backend will now honor the KDE_FULL_SESSION environment variable as found on openSUSE. - Changes from 3.2.1 * SecretService backend: use a different function to check that the backend is functional. The default collection may not exist, but the collection will remain usable in that case. Also, make the error message more verbose. Resolves https://bugs.launchpad.net/bugs/1242412. - Changes from 3.2 * Issue #120: Invoke KeyringBackend.priority during load_keyring to ensure that any keyring loaded is actually viable (or raises an informative exception). * Issue #123: fix removing items. * Correctly escape item name when removing. * Use with statement when working with files. * Add a test for removing one item in group. * Issue #81: Added experimental support for third-party backends. See keyring.core._load_library_extensions for information on supplying a third-party backend. - Changes from 3.1 * All code now runs natively on both Python 2 and Python 3, no 2to3 conversion is required. * Testsuite: clean up, and make more use of unittest2 methods. ------------------------------------------------------------------- Fri Sep 27 07:11:55 UTC 2013 - dmueller@suse.com - update to 3.0.5: * Simplified the implementation of ``keyring.core.load_keyring``. It now uses ``__import__`` instead of loading modules explicitly. * Renamed ``keyring.util.platform`` to ``keyring.util.platform_``. * Ensure that modules are actually imported even in Mercurial's Demand Import environment. * Removed support for Python 2.5. * Removed names in ``keyring.backend`` moved in 1.1 and previously retained for compatibilty. * GnomeKeyring: fix availability checks, and make sure the warning message from pygobject is not printed. * Prioritized backend support. The primary interface for Keyring backend classes has been refactored to now emit a 'priority' based on the current environment (operating system, libraries available, etc). These priorities provide an indication of the applicability of that backend for the current environment. Users are still welcome to specify a particular backend in configuration, but the default behavior should now be to select the most appropriate backend by default. ------------------------------------------------------------------- Wed Sep 4 13:35:14 UTC 2013 - speilicke@suse.com - Update to version 1.6.1: + Only include pytest-runner in 'setup requirements' when ptr invocation is indicated in the command-line (Issue #105). ------------------------------------------------------------------- Fri Jul 19 11:01:08 UTC 2013 - dmueller@suse.com - update to 1.6: - Use the same attributes (``username`` / ``service``) as the SecretService backend uses, allow searching for old ones for compatibility. - Also set ``application`` attribute. - Correctly handle all types of errors, not only ``CANCELLED`` and ``NO_MATCH``. - Avoid printing warnings to stderr when GnomeKeyring is not available. - Use a better label for passwords, the same as GNOME Keyring backend uses. ------------------------------------------------------------------- Wed Jul 3 15:45:06 UTC 2013 - dmueller@suse.com - update to 1.5: * SecretService: allow deleting items created using previous python-keyring versions. * Use secretstorage.get_default_collection if it's available. * Switch GnomeKeyring backend to use native libgnome-keyring via GObject Introspection, not the obsolete python-gnomekeyring module * Use the SecretStorage library to implement the Secret Service backend (instead of using dbus directly) * Now the keyring supports prompting for and deleting passwords - do not unconditionally recommend python-kde4 - python-gnomekeyring is not needed anymore ------------------------------------------------------------------- Fri Mar 22 14:07:23 UTC 2013 - speilicke@suse.com - Recommend both python-gnomekeyring and python-kde4 needed for Gnome and KDE keyring implementations. ------------------------------------------------------------------- Mon Feb 11 09:19:27 UTC 2013 - saschpe@suse.de - Drop old SUSE checks - Add python-unittest2 build requirement to make sure the testsuite passes on SLE_11_SP2 ------------------------------------------------------------------- Sun Feb 10 14:33:59 UTC 2013 - p.drouand@gmail.com - Update to version 1.2.2: * Fixed handling situations when user cancels kwallet dialog or denies access for the app. - Add new dependencies - FIx shebang rpmlint warnings ------------------------------------------------------------------- Fri Jun 8 22:12:52 UTC 2012 - Nico.Laus.2001@gmx.de - update to version 0.9.1 * Fix for issue where SecretServiceBackend.set_password would raise a UnicodeError on Python 3 or when a unicode password was provided on Python 2. * CryptedFileKeyring now uses PBKDF2 to derive the key from the user's password and a random hash. The IV is chosen randomly as well. All the stored passwords are encrypted at once. Any keyrings using the old format will be automatically converted to the new format (but will no longer be compatible with 0.9 and earlier). The user's password is no longer limited to 32 characters. PyCrypto 2.5 or greater is now required for this keyring. - update to version 0.9 * Add support for GTK 3 and secret service D-Bus. Fixes #52. * Issue #60 - Use correct method for decoding. ------------------------------------------------------------------- Wed Apr 11 18:16:14 UTC 2012 - saschpe@gmx.de - Disable testsuite on SLE_11_SP2 to fix build ------------------------------------------------------------------- Tue Apr 3 13:46:06 UTC 2012 - adrian@suse.de - update to version 0.8.1 * file keys are store in a plattform friendly location ------------------------------------------------------------------- Wed Feb 1 10:51:39 UTC 2012 - saschpe@suse.de - Spec file cleanup: * Add proper provides/obsoletes pairs for -gnome and -kde subpackages * Removed outdated %clean section * Package CONTRIBUTORS.txt * Run testsuite - Update to version 0.7.1: * Removed non-ASCII characters from README and CHANGES docs - Changes from version 0.7: * Python 3 is now supported. * Extension modules on Mac and Windows replaced by pure-Python ctypes implementations. Thanks to Jerome Laheurte. * WinVaultKeyring now supports multiple passwords for the same service. * Most of the tests don't require user interaction anymore. * Entries stored in Gnome Keyring appears now with a meaningful name if you try to browser your keyring (for ex. with Seahorse) * Tests from Gnome Keyring no longer pollute the user own keyring. * keyring.util.escape now accepts only unicode strings. Don't try to encode strings passed to it. ------------------------------------------------------------------- Fri Sep 2 08:12:48 UTC 2011 - adrian@suse.de - update to version 0.6.2 * Gnome keyring should not be used if there is no DISPLAY or if the dbus is not around (https://bugs.launchpad.net/launchpadlib/+bug/752282). * Added keyring.http for facilitating HTTP Auth using keyring. * Add a utility to access the keyring from the command line. * Remove a spurious KDE debug message when using KWallet * Fix a bug that caused an exception if the user canceled the KWallet dialog (https://bitbucket.org/kang/python-keyring-lib/issue/37/user-canceling-of-kde-wallet-dialogs). * Now using the existing Gnome and KDE python libs instead of custom C++ code. * Using the getpass module instead of custom code * Fixed the setup script (some subdirs were not included in the release.) * Fixed keyring.core when the user doesn't have a cfg, or is not properly configured. * Fixed escaping issues for usernames with non-ascii characters - -gnome and -kde sub packages became obsolete ------------------------------------------------------------------- Fri Nov 13 12:39:06 UTC 2009 - adrian@suse.de - update to version 0.2 ------------------------------------------------------------------- Fri Sep 4 13:00:31 UTC 2009 - adrian@suse.de - package initial version 0.1
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor
