Date: Tue, 09 Feb 2016 06:40:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 207044] security/py-keyring: Update to 8.3 and add security/py-keyrings.alt Message-ID: <bug-207044-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207044 Bug ID: 207044 Summary: security/py-keyring: Update to 8.3 and add security/py-keyrings.alt 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 166783 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D166783&action= =3Dedit security/py27-keyring-8.3.diff Update security/py-keyring to 8.3. Since version 8.0, they have split some = of the backends into a separate package so I have made a port for that as well (security/py-keyrings.atl, which I will attach here as well). There probably needs to be an UPDATING message about this. For security/py-keyring "portlint -C" reports "looks fine." For security/py-keyrings.alt "portlint -A" reports "looks fine." I will attach the "poudriere testport" logs for both. --- 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 >=3D 1), call:: keyring.core.init_backend(limit=3Dkeyring.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 =3D '/path/to/login.keychain' pw =3D keyring.get_password(...) --- 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. --=20 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-207044-13>