On 2016年12月21日 19:14, Burton, Ross wrote:
On 21 December 2016 at 08:19, <mingli...@windriver.com
<mailto:mingli...@windriver.com>> wrote:
From: Mingli Yu <mingli...@windriver.com
<mailto:mingli...@windriver.com>>
* src/gpgme.h.in <http://gpgme.h.in> (GPGME_STATUS_KEY_CONSIDERED): New.
* src/status-table.c (KEY_CONSIDERED): New.
* src/op-support.c (_gpgme_parse_inv_recp): Add argc KC_FPR and
KC_FLAGS. Use calloc.
(_gpgme_parse_key_considered): New.
* src/sign.c (op_data_t): Add fields KC_FPR and KC_FLAGS.
(release_op_data): Free KC_FPR.
(_gpgme_sign_status_handler): Handle STATUS_KEY_CONSIDERED.
* src/encrypt.c (op_data_t): Add fields KC_FPR and KC_FLAGS.
(release_op_data): Free KC_FPR.
(_gpgme_encrypt_status_handler): Handle STATUS_KEY_CONSIDERED.
Reference:
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=315fb73d4a774e2c699ac1804f5377559b4d0027
<https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=315fb73d4a774e2c699ac1804f5377559b4d0027>
Can you explain *why* we should cherry pick a patch from upstream?
Thanks Ross!
The reason why I cherry pick this patch as there are three failed ptest
cases as below for python-pygpgme which depends on gpgme.
FAIL: test_edit_ownertrust (tests.test_editkey.EditKeyTestCase)
FAIL: test_edit_quit (tests.test_editkey.EditKeyTestCase)
FAIL: test_edit_sign (tests.test_editkey.EditKeyTestCase)
And also found the solution from
https://pagure.io/pygpgme/c/f14699792622715c9cec372400f9dc38f1122f63?branch=master
to fix the failed ptest cases for python-pygpgme, and this solution for
python-pygpgme also needs we update accordingly for gpgme.
Thanks,
Mingli
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
