control: tag -1 +moreinfoDear Jacob,On Fri, May 4, 2018 at 3:27 AM, Jacob Adams <tookmund@gmail.com> wrote:Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "gpgme1.0"
Thanks for your interest in contribution to debian! Changes since the last upload:
gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium
* Rebuild for stretch-backports.
-- Jacob Adams <tookmund@gmail.com> Thu, 26 Apr 2018 13:13:54 -0400
This package will also require libgpgerror, which you can find here:
https://mentors.debian.net/package/libgpg-error
https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc
It already has an RFS: #897045
I would like to be able to use the latest version of GPGME in my GSoC
2018 project. In order to do that I would prefer to use a backport as
the PGP Clean Room CD is based off of stretch.
I see the project seems already released as beta [1], so maybe there'sno need to do this backports upload?
My project does require a newer version of GPGME than is shipped in stretch. However, I didn’t want to wait on the backport, so I’ve been including the deb files directly in my build:
And what's the benefit for this backports pkg? Any new feature or
bugfix you're particularly interested in?
There has been significant improvement in GPGME’s python binding since stretch, and my project relies on these features, such as the new key generation function.
It would be nice to be able to pull these packages from backports instead of including them directly.
Thanks,
Jacob