Skip to content

continue on PROGRESS and PINENTRY_LAUNCHED#20

Merged
jaymzh merged 2 commits into
jaymzh:masterfrom
oleeander:master
Nov 20, 2015
Merged

continue on PROGRESS and PINENTRY_LAUNCHED#20
jaymzh merged 2 commits into
jaymzh:masterfrom
oleeander:master

Conversation

@oleeander

Copy link
Copy Markdown
Contributor

With this change Pius should be compatible with newer versions of GnuPG.

@oleeander oleeander changed the title continue on PROGRESS (e.g. [GNUPG:] PROGRESS need_entropy X 8 16) continue on PROGRESS and PINENTRY_LAUNCHED Nov 2, 2015
@malattia

Copy link
Copy Markdown

I stumbled on this issue too. Please merge these changes.

@jaymzh

jaymzh commented Nov 20, 2015

Copy link
Copy Markdown
Owner

Hey @oleeander - what version are you on? I don't see this with 2.1.9... which is strange.

@malattia

Copy link
Copy Markdown

I have 2.1.9 on Debian. Maybe it's a patch applied to gnupg2 there?

I submitted this bug report to the Debian package too:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805649

On Friday, November 20, 2015, Phil Dibowitz notifications@github.com
wrote:

Hey @oleeander https://github.com/oleeander - what version are you on?
I don't see this with 2.1.9... which is strange.


Reply to this email directly or view it on GitHub
#20 (comment).

mattia
:wq!

@jaymzh

jaymzh commented Nov 20, 2015

Copy link
Copy Markdown
Owner

I'm also on Debian. Weird... Ah well, it's a good PR. Merging. Thanks!

jaymzh added a commit that referenced this pull request Nov 20, 2015
continue on PROGRESS and PINENTRY_LAUNCHED
@jaymzh jaymzh merged commit c1f0fbe into jaymzh:master Nov 20, 2015
@oleeander

Copy link
Copy Markdown
Contributor Author

Thanks for merging. I'm on Arch Linux and GnuPG 2.1.9 with libgcrypt 1.6.4. There aren't any patches applied downsteam:

@jaymzh

jaymzh commented Nov 22, 2015

Copy link
Copy Markdown
Owner

All good. Thanks for the PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants