Summary: | app-crypt/gpgme-1.1.5: tests fail when rebuilding after dev-libs/pth upgrade | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dustin Polke <DuPol> |
Component: | New packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED UPSTREAM | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Dustin Polke
2008-01-14 21:25:05 UTC
Created attachment 140950 [details]
Build log
Updating to pth-2.0.7-r1 and recompiling gnupg and gpgme gives the same failure. Just wanted to try with USE=debug emerge pth, but that removes the libs (see #205875). I left there a note, but not sure you will read it as the bug is closed. So I mention it here as well. Before re-emerging pth, gpgme passed all tests. That was before switching to gnupg-2.0.7. So this might be connected? Question that arises for me, is whether gnupg works right now like it should since tests fail with a bunch of bad password errors... There is a problem with gnupg-2 and gpgme tests, because of this you get: t-edit.c:142: GPGME: Bad passphrase Upstream released gpgme-1.6 with the same problem... They not intend to release patch, so I guess we have to wait for 1.7. Thanks! I suggest to disable the test suite because I found a failure of it quite alerting. Maybe it is possible to conditionally RESTRICT=test, depending on the gnupg version, and put a comment about this behavior in the ebuild referring to upstream so a user is informed. Dustin gpgme-1.6 passes all tests, soon replace this one. |