From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] gnome-bluetooth: fix compile
Date: Mon, 21 Mar 2016 14:10:20 +0100 [thread overview]
Message-ID: <20160321131020.GC2562@jama> (raw)
In-Reply-To: <56EFEC56.3090406@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Mon, Mar 21, 2016 at 02:43:02PM +0200, Alexander Kanavin wrote:
> On 03/18/2016 09:06 PM, alexander.kanavin@linux.intel.com wrote:
> >> fixes error series starting with
> >> | Caught exception: <type 'exceptions.TypeError'> TypeError('expected a
> >> string or other character buffer object',)
> >> | >
> >> /home/superandy/tmp/oe-core-glibc/sysroots/x86_64-linux/usr/lib/python2.7/distutils/sysconfig.py(22)<module>()
> >> | -> PREFIX = os.path.normpath(sys.prefix).replace(
> >> os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
> >
> > Both this patch and the second one should be replaced with a patch that
> > simply adds
> >
> > inherit gobject-introspection
> >
> > to the recipe. For some reason I forgot to do that in my g-i fixes patchset.
>
> Martin, can you drop these patches from master-next please? Just want to
> make sure they don't make it to the master branch.
After someone sends the patch with the inherit, then yes.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-03-21 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 22:13 [PATCH 1/2] gnome-bluetooth: fix compile Andreas Müller
2016-03-16 22:13 ` [PATCH 2/2] gnome-bluetooth: pack introspection related files Andreas Müller
2016-03-18 19:06 ` [PATCH 1/2] gnome-bluetooth: fix compile alexander.kanavin
2016-03-21 12:43 ` Alexander Kanavin
2016-03-21 13:10 ` Martin Jansa [this message]
2016-03-21 13:59 ` Andreas Müller
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=20160321131020.GC2562@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.