From: chalianis1@gmail.com
To: s.hauer@pengutronix.de
Cc: barebox@lists.infradead.org, Chali Anis <chalianis1@gmail.com>
Subject: [PATCH v2 1/5] test: Containerfile: fix build issue related to apt cleanup.
Date: Fri, 12 Dec 2025 00:08:20 -0500 [thread overview]
Message-ID: <20251212050824.1273837-1-chalianis1@gmail.com> (raw)
From: Chali Anis <chalianis1@gmail.com>
We cleanup the apt data after the second install group otherwise we
we have to do an apt update.
=> ERROR [ 3/10] RUN apt-get install -y --no-install-recommends lsb-release gpg &&
wget https://apt.llvm.org/llvm.sh && chmod +x llvm.sh && ./llvm.sh 20 -n trixie 0.3s
------
> [ 3/10] RUN apt-get install -y --no-install-recommends lsb-release gpg &&
wget https://apt.llvm.org/llvm.sh && chmod +x llvm.sh && ./llvm.sh 20 &&
apt-get remove -y lsb-release gnupg &&
apt-get autoremove -y --purge && apt-get clean &&
rm -rf llvm.sh /var/lib/apt/lists/*:
0.240 Reading package lists...
0.258 Building dependency tree...
0.261 Reading state information...
0.266 E: Unable to locate package lsb-release
0.266 E: Unable to locate package gpg
------
1 warning found (use docker --debug to expand):
- MaintainerDeprecated: Maintainer instruction is deprecated in favor of using label (line 6)
Containerfile:67
--------------------
66 |
67 | >>> RUN apt-get install -y --no-install-recommends lsb-release gpg \
68 | >>> && wget https://apt.llvm.org/llvm.sh \
69 | >>> && chmod +x llvm.sh && ./llvm.sh ${LLVM_VERSION} -n trixie \
70 | >>> && apt-get remove -y lsb-release gnupg \
71 | >>> && apt-get autoremove -y --purge \
72 | >>> && apt-get clean \
73 | >>> && rm -rf llvm.sh /var/lib/apt/lists/*
74 |
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get install -y --no-install-recommends
lsb-release gpg \t&& wget https://apt.llvm.org/llvm.sh \t&& chmod +x llvm.sh &&
./llvm.sh ${LLVM_VERSION} -n trixie \t&& apt-get remove -y lsb-release gnupg \t&&
apt-get autoremove -y --purge \t&& apt-get clean \t&&
rm -rf llvm.sh /var/lib/apt/lists/*" did not complete successfully: exit code: 100
Signed-off-by: Chali Anis <chalianis1@gmail.com>
---
test/Containerfile | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/test/Containerfile b/test/Containerfile
index c9e11b45985f..e322fed15727 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -56,9 +56,7 @@ RUN apt-get update && apt-get upgrade && apt-get install -y --no-install-recomme
device-tree-compiler \
u-boot-tools \
yamllint \
- yq \
- && apt-get clean \
- && rm -rf /var/lib/apt/lists/*
+ yq
ENV GCC_VERSION=15.2.0
ENV LLVM_VERSION=20
next reply other threads:[~2025-12-12 5:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 5:08 chalianis1 [this message]
2025-12-12 5:08 ` [PATCH v2 2/5] ci: container: update llvm to 21 and fix dependency issue chalianis1
2025-12-12 14:03 ` Ahmad Fatoum
2025-12-12 5:08 ` [PATCH v2 3/5] test: container: add qemu-efi-aarch64 chalianis1
2025-12-12 14:03 ` Ahmad Fatoum
2025-12-12 5:08 ` [PATCH v2 4/5] test: arm: add efi v8 test for efi arm64 payload chalianis1
2025-12-12 14:05 ` Ahmad Fatoum
2025-12-12 5:08 ` [PATCH v2 5/5] doc: efi: add efi armv8 documentaion chalianis1
2025-12-12 14:06 ` Ahmad Fatoum
2025-12-12 9:20 ` [PATCH v2 1/5] test: Containerfile: fix build issue related to apt cleanup Ahmad Fatoum
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=20251212050824.1273837-1-chalianis1@gmail.com \
--to=chalianis1@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox