From: "Tim Orling" <ticotimo@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Tim Orling <timothy.t.orling@linux.intel.com>
Subject: [PATCH 0/5] Core python3 recipe updates
Date: Tue, 8 Dec 2020 16:35:40 -0800 [thread overview]
Message-ID: <cover.1607473952.git.timothy.t.orling@linux.intel.com> (raw)
From: Tim Orling <timothy.t.orling@linux.intel.com>
Upgrade several recipes to latest versions and fix some deps.
NOTE: python3-packaging 20.7 is available, but we need the next tag
which will re-add setup.py
The following changes since commit e995e67bc7a3d30adf9f8d0d2f4df92a941baeae:
meta/lib/oeqa/manual/oe-core.json: Update test_bitbake_devshell (2020-12-06 23:16:50 +0000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib timo/py3-core-recipe-updates-20201208
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=timo/py3-core-recipe-updates-20201208
Tim Orling (5):
python3-hypothesis: upgrade 5.41.4 -> 5.41.5
python3-importlib-metadata: upgrade 3.1.0 -> 3.1.1
python3-pygments: upgrade v2.7.2 -> v2.7.3
python3-setuptools: upgrade 50.3.2 -> 51.0.0
python3-setuptools-scm: add python3-toml dep
...hon3-hypothesis_5.41.4.bb => python3-hypothesis_5.41.5.bb} | 4 ++--
...-metadata_3.1.0.bb => python3-importlib-metadata_3.1.1.bb} | 4 ++--
.../{python3-pygments_2.7.2.bb => python3-pygments_2.7.3.bb} | 2 +-
meta/recipes-devtools/python/python3-setuptools-scm_4.1.2.bb | 2 ++
...hon3-setuptools_50.3.2.bb => python3-setuptools_51.0.0.bb} | 2 +-
5 files changed, 8 insertions(+), 6 deletions(-)
rename meta/recipes-devtools/python/{python3-hypothesis_5.41.4.bb => python3-hypothesis_5.41.5.bb} (67%)
rename meta/recipes-devtools/python/{python3-importlib-metadata_3.1.0.bb => python3-importlib-metadata_3.1.1.bb} (68%)
rename meta/recipes-devtools/python/{python3-pygments_2.7.2.bb => python3-pygments_2.7.3.bb} (83%)
rename meta/recipes-devtools/python/{python3-setuptools_50.3.2.bb => python3-setuptools_51.0.0.bb} (95%)
--
2.25.0
next reply other threads:[~2020-12-09 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 0:35 Tim Orling [this message]
2020-12-09 0:35 ` [PATCH 1/5] python3-hypothesis: upgrade 5.41.4 -> 5.41.5 Tim Orling
2020-12-09 0:35 ` [PATCH 2/5] python3-importlib-metadata: upgrade 3.1.0 -> 3.1.1 Tim Orling
2020-12-09 0:35 ` [PATCH 3/5] python3-pygments: upgrade v2.7.2 -> v2.7.3 Tim Orling
2020-12-09 0:35 ` [PATCH 4/5] python3-setuptools: upgrade 50.3.2 -> 51.0.0 Tim Orling
2020-12-09 0:35 ` [PATCH 5/5] python3-setuptools-scm: add python3-toml dep Tim Orling
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.1607473952.git.timothy.t.orling@linux.intel.com \
--to=ticotimo@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=timothy.t.orling@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox