All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] #11891 - Port bmaptools to Python 3
Date: Wed,  6 Sep 2017 12:48:22 +0300	[thread overview]
Message-ID: <cover.1504691079.git.ed.bartosh@linux.intel.com> (raw)

Hi,

This patchset switches bmap-tools to usage of native Python 3.
As bmap-tools is the only recipe in oe-core that uses Python 2
this change should help to stop building native Python 2.

The following changes since commit 7a5d997dc264ca8913c5ea57a2c5120a2dc41528:

  wic: selftest: add test_wic_rm_ext test case (2017-09-05 14:28:41 +0300)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/wip
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wip

Ed Bartosh (3):
  bmap-tools: upgrade to v3.4
  bmap-tools: switch to Python 3
  wic: run bmaptool with native Python3

 .../bmap-tools/{bmap-tools_3.2.bb => bmap-tools_3.4.bb}          | 9 +++------
 scripts/lib/wic/plugins/imager/direct.py                         | 6 ++++--
 2 files changed, 7 insertions(+), 8 deletions(-)
 rename meta/recipes-support/bmap-tools/{bmap-tools_3.2.bb => bmap-tools_3.4.bb} (79%)

--
Regards,
Ed



             reply	other threads:[~2017-09-06  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06  9:48 Ed Bartosh [this message]
2017-09-06  9:48 ` [PATCH 1/3] bmap-tools: upgrade to v3.4 Ed Bartosh
2017-09-06 10:15   ` Burton, Ross
2017-09-06  9:48 ` [PATCH 2/3] bmap-tools: switch to Python 3 Ed Bartosh
2017-09-06  9:48 ` [PATCH 3/3] wic: run bmaptool with native Python3 Ed Bartosh
2017-09-06 10:04 ` ✗ patchtest: failure for #11891 - Port bmaptools to Python 3 Patchwork

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=cover.1504691079.git.ed.bartosh@linux.intel.com \
    --to=ed.bartosh@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 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.