-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2017-07-21 at 15:36 +0300, Alexander Bokovoy wrote:
> On pe, 21 heinä 2017, Neal Gompa wrote:
> > On Fri, Jul 21, 2017 at 8:08 AM, Igor Gnatenko
> > wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > Hello,
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2017-07-21 at 08:11 -0400, Neal Gompa wrote:
> On Fri, Jul 21, 2017 at 8:08 AM, Igor Gnatenko
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hello,
> >
> > pygpgme is dead since 2013, I've wrote and applied some p
On pe, 21 heinä 2017, Neal Gompa wrote:
On Fri, Jul 21, 2017 at 8:08 AM, Igor Gnatenko
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
pygpgme is dead since 2013, I've wrote and applied some patches to make
it to work with latest gnupg2/gpgme stack, but since March it FTBFS (so
On Fri, Jul 21, 2017 at 8:08 AM, Igor Gnatenko
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
>
> pygpgme is dead since 2013, I've wrote and applied some patches to make
> it to work with latest gnupg2/gpgme stack, but since March it FTBFS (so
> I added `|| :` for tests). I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
pygpgme is dead since 2013, I've wrote and applied some patches to make
it to work with latest gnupg2/gpgme stack, but since March it FTBFS (so
I added `|| :` for tests). I'm planning to retire pygpgme from F27
right before branching. So just