Bug 552614 – app-crypt/pinentry-0.9.5, app-eselect/eselect-pinentry-0.6, app-crypt/gnupg-2.0.28, dev-libs/libassuan-2.2.1 stable request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pacho Ramos 2015-06-20 09:24:51 UTC]

This is to ensure we get this stabilized with Gnome 3.16

[Comment 1 Kristian Fiskerstrand (RETIRED) 2015-06-20 12:37:41 UTC]

Just to confirm that the following packages should be ready for stabilization when needed as dependencies. If not, we should give it a bit more time in ~arch before calling arches, but I don't expect any issues with them:
=app-crypt/pinentry-0.9.4-r1
=app-eselect/eselect-pinentry-0.5
=app-crypt/gnupg-2.0.28

[Comment 2 Pacho Ramos 2015-06-20 13:06:45 UTC]

That versions are nice, and yes, no problem waiting a bit more. This was mostly for tracking purposes and to ensure they are ready at the time we pretend to stabilize Gnome 3.16

[Comment 3 Kristian Fiskerstrand (RETIRED) 2015-07-01 19:07:00 UTC]

Should make this pinentry 0.9.5 as gcd doesn't really work on lower versions due to dbus issues

[Comment 4 Kristian Fiskerstrand (RETIRED) 2015-07-01 19:11:17 UTC]

Actually this relates to gnupg 2.1.6 as well, mainly: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=816824953c91959c23a57c047bdba6a902ffdde6

[Comment 5 Pacho Ramos 2015-07-03 08:25:01 UTC]

0.9.5 needs one more dependency to go to stable

[Comment 6 Pacho Ramos 2015-07-10 09:25:57 UTC]

lgpg-error is handled in a separate and older report

[Comment 7 Kristian Fiskerstrand (RETIRED) 2015-07-13 08:49:31 UTC]

Please hold off stabilization of pinentry-0.9.5 a bit, just got a report of a possible regression that I need to debug.

[Comment 8 Kristian Fiskerstrand (RETIRED) 2015-09-05 14:12:50 UTC]

Adding libassuan to packages to stabilize for this

[Comment 9 Mikle Kolyada (RETIRED) 2015-09-05 16:52:05 UTC]

amd64 stable

[Comment 10 Jeroen Roovers (RETIRED) 2015-09-08 04:28:29 UTC]

Stable for HPPA PPC64.

[Comment 11 Renato Alves 2015-09-09 18:20:56 UTC]

Hi everyone,

Apologies if this isn't the right place to report this or if it is caused by
something else but, upon upgrade to pinentry-0.9.5 I'm getting a reproducible
crash due to an invalid pointer error.

The current libraries in the system (amd64 - mostly stable packages with a few ~amd64 here an there) are:
pinentry-0.9.5
libassuan-2.2.1
eselect-pinentry-0.6
gnupg-2.0.28

If I downgrade to pinentry-0.9.0 all works normally.

Attached the dump (not sure if it's informative).

[Comment 12 Renato Alves 2015-09-09 18:21:32 UTC]

Created attachment 411444 [details, diff]
Dump produced by pinentry's failure

[Comment 13 Alon Bar-Lev (RETIRED) 2015-09-09 18:29:36 UTC]

(In reply to Renato Alves from comment #11)
> Hi everyone,
> 
> Apologies if this isn't the right place to report this or if it is caused by
> something else but, upon upgrade to pinentry-0.9.5 I'm getting a reproducible
> crash due to an invalid pointer error.

Interesting, please open a new bug, specify exact sequence and emerge --info, also compile the pinentry using FEATURES="nostrip" so we see symbols in the dump.

[Comment 14 Renato Alves 2015-09-10 16:59:22 UTC]

Crash reported as bug 560158.

[Comment 15 Agostino Sarubbo 2015-09-12 08:26:01 UTC]

x86 stable

[Comment 16 Tobias Klausmann (RETIRED) 2015-09-16 09:08:13 UTC]

Stable on alpha.

[Comment 17 Markus Meier 2015-09-27 09:01:31 UTC]

arm stable

[Comment 18 Mikle Kolyada (RETIRED) 2015-10-10 15:50:51 UTC]

sparc stable

[Comment 19 Agostino Sarubbo 2015-11-10 11:50:20 UTC]

ppc stable

[Comment 20 Agostino Sarubbo 2015-11-10 11:50:56 UTC]

ia64 stable. Closing.