All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Yu, Mingli" <mingli.yu@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gpgme: add GPGME_STATUS_KEY_CONSIDERED
Date: Thu, 22 Dec 2016 16:30:58 +0200	[thread overview]
Message-ID: <24ee0d1e-573d-04ec-8cac-e59c9acf593d@linux.intel.com> (raw)
In-Reply-To: <585B397B.6080206@windriver.com>

On 12/22/2016 04:24 AM, Yu, Mingli wrote:
> 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.

pygpgme upstream hasn't released a new version since 2012; the link 
above is someone's fork to fix the pressing issues, and there's no 
indication they will do more fixing. I suggest you just take the 
necessary patches, add them to pygpgme recipe, and update gpgme recipe 
at the same time. You can also review debian/ubuntu's pygpgme packages 
to see what custom patching they have there.

Alex



  reply	other threads:[~2016-12-22 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  8:19 [PATCH] gpgme: add GPGME_STATUS_KEY_CONSIDERED mingli.yu
2016-12-21 11:14 ` Burton, Ross
2016-12-21 12:25   ` Alexander Kanavin
2016-12-22  2:24     ` Yu, Mingli
2016-12-22 14:30       ` Alexander Kanavin [this message]
2016-12-22  1:52   ` Yu, Mingli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=24ee0d1e-573d-04ec-8cac-e59c9acf593d@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.