... with couple of minor bugfixes and critical bugfix which prevents DNF to work with GPG verification[0].
Some time ago DNF tests started failing in koschei after update of gnupg2 to 2.1.13. I bisected it and found that they added some new flag which helps to get more information about certificate[1] - STATUS_KEY_CONSIDERED. I found that upstream of gpgme also reacted on that feature[2], so I backported it in our package[3]. And finally made patch to fix problem in pygpgme[4].
Alogn with this I realized that pygpgme spec needs some love (like cleaning stuff, adding %check section to run tests, backporting patches) and renaming, so I sent new one for review[5] and created repo with our (Fedora) fixes on top of dead upstream package[6].
Packagers, feel free to start depending on python2- subpackage as it has been splitted from main pkg.
tl;dr; pygpgme has been fixed and renamed to python-pygpgme has been fixed (and automatically DNF), just test and leave +1 for f23[7] and f24[8].
Thanks for attention!
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1359521 [1] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=ff71521d9698... [2] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=315fb73d4a77... [3] http://pkgs.fedoraproject.org/cgit/rpms/gpgme.git/commit/?id=ffc545a8fdafac6... [4] https://pagure.io/pygpgme/c/f14699792622715c9cec372400f9dc38f1122f63?branch=... [5] https://bugzilla.redhat.com/show_bug.cgi?id=1358357 [6] https://pagure.io/pygpgme [7] https://bodhi.fedoraproject.org/updates/FEDORA-2016-33b89975fe [8] https://bodhi.fedoraproject.org/updates/FEDORA-2016-198d93bc53
Hi,
On Mon, Jul 25, 2016 at 07:02:44PM +0200, Igor Gnatenko wrote:
Alogn with this I realized that pygpgme spec needs some love (like cleaning stuff, adding %check section to run tests, backporting patches) and renaming, so I sent new one for review[5] and created repo with our (Fedora) fixes on top of dead upstream package[6].
This is awesome. Did you by any chance get in touch with other distributions to get them switch to the new fork as well?
Kind regards Till
On Sun, Nov 20, 2016 at 10:18 AM, Till Maas opensource@till.name wrote:
Hi,
On Mon, Jul 25, 2016 at 07:02:44PM +0200, Igor Gnatenko wrote:
Alogn with this I realized that pygpgme spec needs some love (like cleaning stuff, adding %check section to run tests, backporting patches) and renaming, so I sent new one for review[5] and created repo with our (Fedora) fixes on top of dead upstream package[6].
This is awesome. Did you by any chance get in touch with other distributions to get them switch to the new fork as well?
No, I didn't. Unfortunately I don't know what's the usual way of doing this. Help is very welcomed!
Actually since gpgme-1.7.0 it should include py2/py3 bindings and all people who are using pygpgme are encouraged to use official bindings. Unfortunately it's still not available in fedora as we stuck with 1.6.0, because there are some problems with libgcrypt-x.y.z.
Kind regards Till _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org
On Sun, Nov 20, 2016 at 10:37 AM, Igor Gnatenko ignatenko@redhat.com wrote:
On Sun, Nov 20, 2016 at 10:18 AM, Till Maas opensource@till.name wrote:
Hi,
On Mon, Jul 25, 2016 at 07:02:44PM +0200, Igor Gnatenko wrote:
Alogn with this I realized that pygpgme spec needs some love (like cleaning stuff, adding %check section to run tests, backporting patches) and renaming, so I sent new one for review[5] and created repo with our (Fedora) fixes on top of dead upstream package[6].
This is awesome. Did you by any chance get in touch with other distributions to get them switch to the new fork as well?
No, I didn't. Unfortunately I don't know what's the usual way of doing this. Help is very welcomed!
Actually since gpgme-1.7.0 it should include py2/py3 bindings and all people who are using pygpgme are encouraged to use official bindings. Unfortunately it's still not available in fedora as we stuck with 1.6.0, because there are some problems with libgcrypt-x.y.z.
I'm a bit wrong here, we can get 1.7.0 and I'm working on it: https://bugzilla.redhat.com/show_bug.cgi?id=1378056.
Kind regards Till _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org
-- -Igor Gnatenko
-
Igor Gnatenko -
Till Maas