From: Tim Orling <ticotimo@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Recipe upgrades from AUH 2023-02-16
Date: Thu, 16 Feb 2023 15:58:29 -0800 [thread overview]
Message-ID: <cover.1676580166.git.tim.orling@konsulko.com> (raw)
Recipe upgrades from the AUH run on 2023-02-16
The following changes since commit 44311c454d0b0856f58cfa6fa60669903b2ba3af:
yocto-bsps: remove 5.19 bbappend (2023-02-15 10:21:35 +0000)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib timo/recipe-upgrades
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=timo/recipe-upgrades
Tim Orling (3):
python3-hypothesis: upgrade 6.66.0 -> 6.68.1
python3-typing-extensions: upgrade 4.4.0 -> 4.5.0
python3-cryptography{-vectors}: 39.0.0 -> 39.0.1
...vectors_39.0.0.bb => python3-cryptography-vectors_39.0.1.bb} | 2 +-
...n3-cryptography_39.0.0.bb => python3-cryptography_39.0.1.bb} | 2 +-
...ython3-hypothesis_6.66.0.bb => python3-hypothesis_6.68.1.bb} | 2 +-
...g-extensions_4.4.0.bb => python3-typing-extensions_4.5.0.bb} | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/python/{python3-cryptography-vectors_39.0.0.bb => python3-cryptography-vectors_39.0.1.bb} (90%)
rename meta/recipes-devtools/python/{python3-cryptography_39.0.0.bb => python3-cryptography_39.0.1.bb} (95%)
rename meta/recipes-devtools/python/{python3-hypothesis_6.66.0.bb => python3-hypothesis_6.68.1.bb} (91%)
rename meta/recipes-devtools/python/{python3-typing-extensions_4.4.0.bb => python3-typing-extensions_4.5.0.bb} (91%)
--
2.30.2
next reply other threads:[~2023-02-16 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:58 Tim Orling [this message]
2023-02-16 23:58 ` [PATCH 1/3] python3-hypothesis: upgrade 6.66.0 -> 6.68.1 Tim Orling
2023-02-16 23:58 ` [PATCH 2/3] python3-typing-extensions: upgrade 4.4.0 -> 4.5.0 Tim Orling
2023-02-16 23:58 ` [PATCH 3/3] python3-cryptography{-vectors}: 39.0.0 -> 39.0.1 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.1676580166.git.tim.orling@konsulko.com \
--to=ticotimo@gmail.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.