All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>,
	openembedded-core@lists.openembedded.org, ross.burton@intel.com
Subject: Re: [PATCH 7/8] gpgme: 1.8.0 -> 1.9.0
Date: Thu, 17 Aug 2017 08:34:27 +0100	[thread overview]
Message-ID: <1502955267.13978.181.camel@linuxfoundation.org> (raw)
In-Reply-To: <81560385801247ea5c615b7c21dbf9ed199e6492.1502869419.git.hongxu.jia@windriver.com>

On Wed, 2017-08-16 at 04:31 -0400, Hongxu Jia wrote:
> Rebase patches:
> - pkgconfig.patch -> 0001
> - python-lang-config.patch -> 0002
> - 0001-Correctly-install-python-modules.patch -> 0003
> - python-import.patch -> 0004
> - 0001-gpgme-config-skip-all-lib-or-usr-lib-directories-in-.patch ->
> 0005

Looks like there is some kind of python packaging issue:

https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/1185/steps/BuildImages/logs/stdio

Cheers,

Richard



  reply	other threads:[~2017-08-17  7:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  8:31 [PATCH 0/8] upgrade 8 recipes Hongxu Jia
2017-08-16  8:31 ` [PATCH 1/8] apr-util: 1.5.4 -> 1.6.0 Hongxu Jia
2017-08-16  8:31 ` [PATCH 2/8] bash: 4.3.30 -> 4.4 Hongxu Jia
2017-08-17 12:54   ` Richard Purdie
2017-08-16  8:31 ` [PATCH 3/8] dhcp: 4.3.5 -> 4.3.6 Hongxu Jia
2017-08-16  8:31 ` [PATCH 4/8] elfutils: 0.168 -> 0.170 Hongxu Jia
2017-08-16  8:31 ` [PATCH 5/8] libgcrypt: 1.7.8 -> 1.8.0 Hongxu Jia
2017-08-16  8:31 ` [PATCH 6/8] gnupg: 2.1.20 -> 2.1.23 Hongxu Jia
2017-08-18  9:38   ` Richard Purdie
2017-08-16  8:31 ` [PATCH 7/8] gpgme: 1.8.0 -> 1.9.0 Hongxu Jia
2017-08-17  7:34   ` Richard Purdie [this message]
2017-08-17  8:35     ` [PATCH] gpgme: remove local m4/python.m4 Hongxu Jia
2017-08-17  9:23       ` Richard Purdie
2017-08-16  8:31 ` [PATCH 8/8] ncurses: 6.0+20161126 -> 6.0+20170715 Hongxu Jia

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=1502955267.13978.181.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.