Date: Mon, 16 Nov 2015 03:05:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 204582] [maintainer update] security/py-keyring: Update to 5.6 Message-ID: <bug-204582-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204582 Bug ID: 204582 Summary: [maintainer update] security/py-keyring: Update to 5.6 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: douglas@douglasthrift.net Created attachment 163170 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163170&action=edit py27-keyring-5.6.diff Update security/py-keyring to 5.6. Depends on bug 204576, bug 204579, and bug 204581. >From CHANGES.rst: --- 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. --- 5.4 --- * Prefer setuptools_scm to hgtools. --- 5.3 --- * Prefer hgtools to setuptools_scm due to `setuptools_scm #21 <https://bitbucket.org/pypa/setuptools_scm/issue/21>`_. --- 5.2 --- * Prefer setuptools_scm to hgtools. --- 5.1 --- * Host project at Github (`repo <https://github.com/jaraco/keyring>`_). --- 5.0 --- * Version numbering is now derived from the code repository tags via `hgtools <https://pypi.python.org/pypi/hgtools>`_. * Build and install now requires setuptools. ----- 4.1.1 ----- * The entry point group must look like a module name, so the group is now "keyring.backends". --- 4.1 --- * Added preliminary support for loading keyring backends through ``setuptools entry points``, specifically "keyring backends". --- 4.0 --- * 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. --- 3.8 --- * 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. --- 3.7 --- * Gnome keyring no longer relies on the GNOME_KEYRING_CONTROL environment variable. * Issue #140: Restore compatibility for older versions of PyWin32. --- 3.6 --- * `Pull Request #1 (github) <https://github.com/jaraco/keyring/pull/1>`_: Add support for packages that wish to bundle keyring by using relative imports throughout. --- 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. --- 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. --- 3.3 --- * Pull request #40: KWallet backend will now honor the ``KDE_FULL_SESSION`` environment variable as found on openSUSE. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204582-13>