Summary: | 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 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alonbl, esigra |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 552938 | ||
Bug Blocks: | 551826, 565086 | ||
Attachments: | Dump produced by pinentry's failure |
Description
Pacho Ramos
2015-06-20 09:24:51 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 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 Should make this pinentry 0.9.5 as gcd doesn't really work on lower versions due to dbus issues 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 0.9.5 needs one more dependency to go to stable lgpg-error is handled in a separate and older report Please hold off stabilization of pinentry-0.9.5 a bit, just got a report of a possible regression that I need to debug. Adding libassuan to packages to stabilize for this amd64 stable Stable for HPPA PPC64. 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). Created attachment 411444 [details, diff]
Dump produced by pinentry's failure
(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. Crash reported as bug 560158. x86 stable Stable on alpha. arm stable sparc stable ppc stable ia64 stable. Closing. |