Re: [HEADS UP] broken/fixed gnupg2-2.1.13 and pygpgme renamed to python-pygpgme

On Sun, Nov 20, 2016 at 10:37 AM, Igor Gnatenko wrote: > On Sun, Nov 20, 2016 at 10:18 AM, Till Maas 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

Re: [HEADS UP] broken/fixed gnupg2-2.1.13 and pygpgme renamed to python-pygpgme

On Sun, Nov 20, 2016 at 10:18 AM, Till Maas 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)

Re: [HEADS UP] broken/fixed gnupg2-2.1.13 and pygpgme renamed to python-pygpgme

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)

[HEADS UP] broken/fixed gnupg2-2.1.13 and pygpgme renamed to python-pygpgme

... 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