File python-keyring.changes of Package python-keyring

Overview Repositories Revisions Requests Users Attributes Meta

File python-keyring.changes of Package python-keyring (Revision ef1b66908be5227bed43e4d5ff3e4d12)

Currently displaying revision ef1b66908be5227bed43e4d5ff3e4d12 , Show latest

-------------------------------------------------------------------
Wed May  3 16:03:08 UTC 2017 - toddrme2178@gmail.com

- Implement single-spec version.
- Fix source URL.
- Update to version 10.3.2
  * #267: More leniently unescape lowercased characters as
    they get re-cased by ConfigParser.
- Update to version 10.3.1
  * #266: Use private compatibity model rather than six to
    avoid the dependency.
- Update to version 10.3
  * #264: Implement devpi hook for supplying a password when
    logging in with `devpi <https://pypi.org/project/devpi>`_
    client.
  * #260: For macOS, added initial API support for internet
    passwords.

-------------------------------------------------------------------
Mon Jan 16 18:18:33 UTC 2017 - michael@stroeder.com

- update copyright year
- update to 10.2 (requires python-setuptools_scm>=1.15.0)

10.2
----
* #259: Allow to set a custom application attribute for
  SecretService backend.
10.1
----
* #253: Backends now expose a '.name' attribute suitable
  for identifying each backend to users.

-------------------------------------------------------------------
Sat Nov 12 15:17:19 UTC 2016 - michael@stroeder.com

- update to 10.0.2
- build requires python-tox instead of python-pytest-runner
10.0.2
-----
* #247: Restored console script.
10.0.1
------
* Update readme to reflect test recommendations.
10.0
----
* Drop support for Python 3.2.
* Test suite now uses tox instead of pytest-runner.
  Test requirements are now defined in tests/requirements.txt.

-------------------------------------------------------------------
Fri Aug 12 21:41:15 UTC 2016 - michael@stroeder.com

- updated project URL
- update to 9.3.1:
  * Link to the new Gitter chat room is now in the
    readme.
  * Issue #235: ``kwallet`` backend now returns
    string objects instead of ``dbus.String`` objects,
    for less surprising reprs.
  * Minor doc fixes.

-------------------------------------------------------------------
Wed Jun 29 13:34:12 UTC 2016 - tbechtold@suse.com

- update to 9.3:
9.3
---
* Pull Request #226: In SecretService backend, unlock
  individual entries.
9.2.1
-----
* Issue #230: Don't rely on dbus-python and instead
  defer to SecretStorage to describe the installation
  requirements.
9.2
---
* Issue #231 via #233: On Linux, ``secretstorage``
  is now a declared dependency, allowing recommended
  keyring to work simply after installation.
9.1
---
* Issue #83 via #229: ``kwallet`` backend now stores
  the service name as a folder name in the backend rather
  than storing all passwords in a Python folder.
- Adjust Requires
- Use pypi.io for Source url
-------------------------------------------------------------------
Sat Jun  4 12:26:06 UTC 2016 - michael@stroeder.com

- require python-setuptools (see bsc#983147)

-------------------------------------------------------------------
Thu May  5 17:13:09 UTC 2016 - michael@stroeder.com

- update to upstream release 9.0

9.0
---

* Issue #217: Once again, the OS X backend uses the
  Framework API for invoking the Keychain service.
  As a result, applications utilizing this API will be
  authorized per application, rather than relying on the
  authorization of the 'security' application. Consequently,
  users will be prompted to authorize the system Python
  executable and also new Python executables, such as
  those created by virtualenv.

8.7
---

* Changelog now links to issues and provides dates of
  releases.

8.6
---

* Issue #217: Add warning in OS Keyring when 'store'
  is set to 'internet' to determine if this feature is
  used in the wild.

8.5.1
-----

* Pull Request #216: Kwallet backend now has lower
  priority than the preferred SecretService backend,
  now that the desktop check is no longer in place.

8.5
---

* Issue #168: Now prefer KF5 Kwallet to KF4. Users relying
  on KF4 must use prior releases.

8.4
---

* Pull Request #209: Better error message when no backend is
  available (indicating keyrings.alt as a quick workaround).
* Pull Request #208: Fix pywin32-ctypes package name in
  requirements.

8.3
---

* Issue #207: Library now requires win32ctypes on Windows
  systems, which will be installed automatically by
  Setuptools 0.7 or Pip 6 (or later).
* Actually removed QtKwallet, which was meant to be dropped in
  8.0 but somehow remained.

8.2
---

* Update readme to include how-to use with Linux
  non-graphical environments.

8.1
---

* Issue #197: Add ``__version__`` attribute to keyring module.

8.0
---

* Issue #117: Removed all but the preferred keyring backends
  for each of the major desktop platforms:

- keyring.backends.kwallet.DBusKeyring
    - keyring.backends.OS_X.Keyring
    - keyring.backends.SecretService.Keyring
    - keyring.backends.Windows.WinVaultKeyring

All other keyrings
  have been moved to a new package, `keyrings.alt
  <https://pypi.python.org/pypi/keyrings.alt>`_ and
  backward-compatibility aliases removed.
  To retain
  availability of these less preferred keyrings, include
  that package in your installation (install both keyring
  and keyrings.alt).

As these keyrings have moved, any keyrings indicated
  explicitly in configuration will need to be updated to
  replace "keyring.backends." with "keyrings.alt.". For
  example, "keyring.backends.file.PlaintextKeyring"
  becomes "keyrings.alt.file.PlaintextKeyring".

7.3.1
-----

* Issue #194: Redirect away from docs until they have something
  more than the changelog. Users seeking the changelog will
  want to follow the `direct link
  <https://pythonhosted.org/keyring/history.html>`_.

7.3
---

* Issue #117: Added support for filtering which
  backends are acceptable. To limit to only loading recommended
  keyrings (those with priority >= 1), call::

keyring.core.init_backend(limit=keyring.core.recommended)

7.2
---

* Pull Request #190: OS X backend now exposes a ``keychain``
  attribute, which if set will be used by ``get_password`` when
  retrieving passwords. Useful in environments such as when
  running under cron where the default keychain is not the same
  as the default keychain in a login session. Example usage::

keyring.get_keyring().keychain = '/path/to/login.keychain'
    pw = keyring.get_password(...)

-------------------------------------------------------------------
Tue Jan 12 16:56:53 UTC 2016 - michael@stroeder.com

- update to upstream release 7.1.2
- require Python 2.7+
- require python-setuptools_scm 1.9+

7.1
* Issue #186: Removed preference for keyrings based on
  ``XDG_CURRENT_DESKTOP`` as these values are to varied
  to be a reliable indicator of which keyring implementation
  might be preferable.

7.0.2
* Issue #187: Restore ``Keyring`` name in ``kwallet`` backend.
  Users of keyring 6.1 or later should prefer an explicit reference
  to DBusKeyring or QtKeyring instead.

7.0.1
* Issue #183 and Issue #185: Gnome keyring no longer relies
  on environment variables, but instead relies on the GnomeKeyring
  library to determine viability.

7.0
* Issue #99: Keyring now expects the config file to be located
  in the XDG_CONFIG_HOME rather than XDG_DATA_HOME and will
  fail to start if the config is found in the old location but not
  the new. On systems where the two locations are distinct,
  simply copy or symlink the config to remain compatible with
  older versions or move the file to work only with 7.0 and later.
* Replaced Pull Request #182 with a conditional SessionBus
  construction, based on subsequent discussion.

6.1.1
* Pull Request #182: Prevent DBus from indicating as a viable
  backend when no viable X DISPLAY variable is present.

6.1
* Pull Request #174: Add DBus backend for KWallet, preferred to Qt
  backend. Theoretically, it should be auto-detected based on
  available libraries and interchangeable with the Qt backend.

6.0
* Drop support for Python 2.6.

5.7.1
* Updated project metadata to match Github hosting and
  generally refreshed the metadata structure to match
  practices with other projects.

-------------------------------------------------------------------
Fri Dec 11 14:45:37 UTC 2015 - michael@stroeder.com

- Update to version 5.7
- Removed CONTRIBUTORS.txt because not available in upstream
  source anymore.
- dropped patches keyring-import-gi.patch and keyring-gnome-3.18.patch
  because they were obsoleted by fixes in upstream source

5.7
---
* Issue #177: Resolve default keyring name on Gnome using the API.
* Issue #145: Add workaround for password exposure through
  process status for most passwords containing simple
  characters.
5.6
---
* Allow keyring to be invoked from command-line with
  ``python -m keyring``.
5.5.1
-----
* Issue #156: Fixed test failures in ``pyfs`` keyring related to
  0.5 release.
5.5
---
* Pull Request #176: Use recommended mechanism for checking
  GnomeKeyring version.

-------------------------------------------------------------------
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

Places

File python-keyring.changes of Package python-keyring (Revision ef1b66908be5227bed43e4d5ff3e4d12)

Places