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

Bug#897642: marked as done (RFS: gpgme1.0/1.11.1-1~bpo9+1)

Your message dated Sun, 9 Sep 2018 14:55:20 +0900
with message-id <CAEQ9gE=cig0kXJYQuAybxZ8eV=32Zx-FNo_NCPdvoxbi5s7D4g@mail.gmail.com>
and subject line Re: Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1
has caused the Debian Bug report #897642,
regarding RFS: gpgme1.0/1.11.1-1~bpo9+1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
897642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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


--- End Message ---
--- Begin Message --- 
On Sun, Sep 2, 2018 at 5:36 AM, Jacob Adams <tookmund@gmail.com> wrote:
>
>> On Sep 1, 2018, at 12:45, Roger Shimizu <rogershimizu@gmail.com> wrote:
>>
>> 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.
>>
>
> Should’ve mentioned that it required a newer version of libgpg-error sorry. Thanks for fixing that and updating the backport.
>
>> I uploaded this backported pkg to DELAYED=6.
>> So If you don't like the backports upload, just kindly cancel it.

Both gpgme1.0 and libgpg-error are already in backports NEW queue.
So I'm closing this ticket.

> Thank you!
> Looking into why you did a gnupg2 backport I probably should use that too, to support newer ECC keys.

Please do so.
Thanks for your work!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

--- End Message ---
Reply to: