On 2016年12月21日 20:25, Alexander Kanavin wrote:
On 12/21/2016 01:14 PM, Burton, Ross wrote:
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?
Because someone didn't check RRS, which would suggest an update to gpgme
1.8.0 should be done instead.
http://recipes.yoctoproject.org/rrs/recipedetail/834/
Thanks Alex!
Actually I ever tried to upgrade gpgme to 1.8.0 before send out this
patch, but there comes other ptest failed issues for python-pygpgme
which not exist on current gpgme 1.6.0 if we simply update gpgme to 1.8.0.
Anyway I prefer to wait for more update for python-pygpgme from
https://pagure.io/pygpgme/commits/master before we move forward to gpgme
1.8.0.
Thanks,
Mingli
Alex
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
