From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] ofono: update to 1.18
Date: Mon, 16 May 2016 14:59:48 +0300 [thread overview]
Message-ID: <5739B634.3010603@linux.intel.com> (raw)
In-Reply-To: <20160516115415.GA21937@mbabyjoh-desk.ger.corp.intel.com>
On 05/16/2016 02:54 PM, Maxin B. John wrote:
>> Maxin can cherry-pick one of my patches, or just postpone the version update
>> until the py3 patchset is merged:
>>
>> https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=akanavin/deprecate-python2&id=6f7eac37a25f1ab55a28cac7b15674dcd6962404
>
> I have tried this patch before sending the upgrades and had to abandon the
> attempt because of the newly introduced dependency on python3-pygobject.
>
> Guess the best way forward will be to wait till py3 patchset is merged :)
That's right; oe-core will move python-pygobject to python 3, all
dependent oe-core recipes will be moved to use that, and original
py2-based python-pygobject will be added to meta-oe to avoid breakage in
3rd party layers (and it needs fixing because it installs same files in
same locations as py3 based version).
The whole thing snowballs pretty quickly, and I'm not even attempting to
move meta-oe to python 3.
Alex
prev parent reply other threads:[~2016-05-16 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 13:16 [PATCH 1/3] ofono: update to 1.18 Maxin B. John
2016-05-12 13:16 ` [PATCH 2/3] connman: update to version 1.32 Maxin B. John
2016-05-12 13:16 ` [PATCH 3/3] mmc-utils: update to latest git version Maxin B. John
2016-05-14 6:23 ` [PATCH 1/3] ofono: update to 1.18 Richard Purdie
2016-05-16 11:46 ` Alexander Kanavin
2016-05-16 11:54 ` Maxin B. John
2016-05-16 11:59 ` Alexander Kanavin [this message]
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=5739B634.3010603@linux.intel.com \
--to=alexander.kanavin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox