From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: [PATCH 2/5] Dockerfile: Add python3-pycryptodome
Date: Thu, 20 Jun 2024 07:19:34 -0600 [thread overview]
Message-ID: <20240620131937.1130446-3-sjg@chromium.org> (raw)
In-Reply-To: <20240620131937.1130446-1-sjg@chromium.org>
This is used by some Binman entry types, so add it to allow more tests
to pass.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
tools/docker/Dockerfile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index 0941b0f6952..a23504179c2 100644
--- a/tools/docker/Dockerfile
+++ b/tools/docker/Dockerfile
@@ -98,6 +98,7 @@ RUN apt-get update && apt-get install -y \
python2.7 \
python3 \
python3-coverage \
+ python3-pycryptodome \
python3-dev \
python3-pip \
python3-pyelftools \
--
2.34.1
next prev parent reply other threads:[~2024-06-20 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 13:19 [PATCH 0/5] Add Binman code-coverage test to CI Simon Glass
2024-06-20 13:19 ` [PATCH 1/5] Dockerfile: Add python3-coverage Simon Glass
2024-06-20 14:30 ` Tom Rini
2024-06-20 13:19 ` Simon Glass [this message]
2024-06-20 13:19 ` [PATCH 3/5] buildman: Support building within a Python venv Simon Glass
2024-06-20 13:38 ` Heinrich Schuchardt
2024-06-20 23:05 ` Simon Glass
2024-06-20 14:32 ` Tom Rini
2024-06-20 23:05 ` Simon Glass
2024-06-20 23:30 ` Tom Rini
2024-06-21 14:57 ` Simon Glass
2024-06-21 15:22 ` Tom Rini
2024-06-21 18:19 ` Simon Glass
2024-06-21 19:26 ` Tom Rini
2024-06-21 19:39 ` Simon Glass
2024-06-21 20:48 ` Tom Rini
2024-06-20 13:19 ` [PATCH 4/5] u_boot_pylib: Use correct coverage tool within venv Simon Glass
2024-06-20 13:19 ` [PATCH 5/5] CI: Run code-coverage test for Binman Simon Glass
2024-06-20 14:34 ` Tom Rini
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=20240620131937.1130446-3-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.