[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1



Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "gpgme1.0"

 * Package name    : gpgme1.0
   Version         : 1.11.1-1~bpo9+1
   Upstream Author : GnuPG developers <gnupg-devel@gnupg.org>
 * URL             : https://gnupg.org/software/gpgme/index.html
 * License         : LGPL-2.1+
   Section         : libs

  It builds those binary packages:

 libgpgme-dev - GPGME - GnuPG Made Easy (development files)
 libgpgme11 - GPGME - GnuPG Made Easy (library)
 libgpgmepp-dev - C++ and Qt bindings for GPGME (development files)
 libgpgmepp-doc - C++ and Qt bindings for GPGME (documentation for
developers)
 libgpgmepp6 - C++ wrapper library for GPGME
 libqgpgme7 - library for GPGME integration with Qt
 python-gpg - Python interface to the GPGME GnuPG encryption library
(Python 2)
 python3-gpg - Python interface to the GPGME GnuPG encryption library
(Python 3)

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/gpgme1.0


  Alternatively, one can download the package with dget using this command:

    dget -x
https://mentors.debian.net/debian/pool/main/g/gpgme1.0/gpgme1.0_1.11.1-1~bpo9+1.dsc


  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.

Thanks,
Jacob

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: