On 2013-06-08 15:06:11, Dmitry Shachnev wrote: > Hi, I would like to request sponsorship of python-keyring package. This > is a major update, done with maintainer's permission. > > Changelog: > > * New upstream release. > * Switch debian/watch to use .tar.bz2 archives from BitBucket, rather than > .zip archives from PyPI; drop unzip build-dependency. > * Recommend python[3]-secretstorage, as the default backend now uses it. > * Suggest python[3]-gi and gir1.2-gnomekeyring-1.0, as the GNOME Keyring > backend now uses it. > * Suggest python-gdata and python-keyczar, as other backends use them. > * Drop all previous patches, applied upstream. > * debian/patches/no-pytest-runner.patch: do not require pytest-runner, > it is not in Debian. > * Bump Standards-Version to 3.9.4 and debhelper compat level to 9. > * Disable HTTP traffic in debian/rules. > * Run upstream testsuite during build; simplify other debian/rules parts. > * Build-depend on python[3]-mock and python[3]-crypto, for the testsuite. > * Remove build directory in clean target. > * Update some file names to match upstream renamings.
If nobody beats me to it, I'll take a look at it later next weak. Did you have a look at the open bugs? Also, 1.0 dropped support for the auto-conversion of pre-0.9 Crypto based backends. Although wheezy has the code to convert the the storage, I think it'd be a good idea to at least mention the fact in NEWS.Debian and maybe also provide a script to convert old keyrings. Regards -- Sebastian Ramacher
signature.asc
Description: Digital signature
