Re: Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1
[ Resend for the record with the lists below ]
+ debian-backports@l.d.o
+ pkg-gnupg-maint@l.alioth.d.o
On Sat, Sep 1, 2018 at 11:15 PM, Jacob Adams <tookmund@gmail.com> wrote:
> control: tag -1 -moreinfo
>
> On Sep 1, 2018, at 04:49, Roger Shimizu <rogershimizu@gmail.com> wrote:
>
> control: tag -1 +moreinfo
>
> Dear 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's
> no 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:
> https://salsa.debian.org/tookmund-guest/make-pgp-clean-room/tree/master/resources/config/packages.chroot
>
>
> 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.
I compiled this pkg under stretch, and meet the following error.
====
cJSON.c:45:20: fatal error: gpgrt.h: No such file or directory
# include <gpgrt.h>
^
====
I see you updated libgpg-error to 1.29, so I tried to compile with
latest backported sid version, 1.32, and it succeeded.
So I updated D-B on libgpg-error to >= 1.29.
I uploaded this backported pkg to DELAYED/6.
So If you don't like the backports upload, just kindly cancel it.
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
Reply to: