From: Armin Kuster <akuster808@gmail.com>
To: akuster808@gamil.com, openembedded-devel@lists.openembedded.org
Subject: [Rocko][PATCH 0/4] small pull request
Date: Thu, 7 Jun 2018 06:52:15 -0700 [thread overview]
Message-ID: <cover.1528379391.git.akuster808@gmail.com> (raw)
Please consider these changes for rocko
The following changes since commit dacfa2b1920e285531bec55cd2f08743390aaf57:
python-automat: fix build dependencies to avoid download during do_compile (2018-03-12 14:43:28 -0700)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded rocko-next
http://cgit.openembedded.org/cgit.cgi/meta-openembedded/log/?h=rocko-next
Armin Kuster (2):
wireshark: Update to 2.2.11
wireshark: Update Package to 2.2.12
Philip Balister (1):
protobuf: Fix fetcher failure for rocko.
Ricardo Salveti (1):
python3-asn1crypto: add support for Python 3
.../wireshark/{wireshark_2.2.10.bb => wireshark_2.2.12.bb} | 6 +++---
meta-oe/recipes-devtools/protobuf/protobuf_3.4.1.bb | 2 +-
meta-python/recipes-devtools/python/python3-asn1crypto_0.23.0.bb | 2 ++
3 files changed, 6 insertions(+), 4 deletions(-)
rename meta-networking/recipes-support/wireshark/{wireshark_2.2.10.bb => wireshark_2.2.12.bb} (92%)
create mode 100644 meta-python/recipes-devtools/python/python3-asn1crypto_0.23.0.bb
--
2.7.4
next reply other threads:[~2018-06-07 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 13:52 Armin Kuster [this message]
2018-06-07 13:52 ` [PATCH 1/4] wireshark: Update to 2.2.11 Armin Kuster
2018-06-07 13:52 ` [PATCH 2/4] wireshark: Update Package to 2.2.12 Armin Kuster
2018-06-07 13:52 ` [PATCH 3/4] python3-asn1crypto: add support for Python 3 Armin Kuster
2018-06-07 13:52 ` [PATCH 4/4] protobuf: Fix fetcher failure for rocko Armin Kuster
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.1528379391.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster808@gamil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox