From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH 1/1] dpkg-prebuilt: ensure fetched packages are valid debian packages
Date: Wed, 26 Jun 2024 13:22:29 +0000 [thread overview]
Message-ID: <1b58f74001e7ecb5fe027a3ce5929fb7fcfce287.camel@siemens.com> (raw)
In-Reply-To: <20240626110541.94885-1-felix.moessbauer@siemens.com>
On Wed, 2024-06-26 at 13:05 +0200, Felix Moessbauer wrote:
> In case of dpkg-prebuilt, we need to check if the fetched packages
> are
> valid debian packages to only deploy valid ones into the sstate
> cache.
> Otherwise broken packages might end up in the cache and break future
> builds.
This does not work in case we deploy multiple debs. Will fix this in a
v2 after testing.
Felix
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/classes/dpkg-prebuilt.bbclass | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/dpkg-prebuilt.bbclass b/meta/classes/dpkg-
> prebuilt.bbclass
> index 7092670b..c6b66c62 100644
> --- a/meta/classes/dpkg-prebuilt.bbclass
> +++ b/meta/classes/dpkg-prebuilt.bbclass
> @@ -19,5 +19,8 @@ python do_unpack:prepend() {
> # also breaks inherited (from dpkg-base) dependency on sbuild_chroot
> do_dpkg_build[depends] = "${PN}:do_unpack"
> do_dpkg_build() {
> - true
> + # ensure all packages we got are valid debian packages
> + if [ -n "$(find ${WORKDIR} -maxdepth 1 -name '*.deb' -print -
> quit)" ]; then
> + dpkg -I ${WORKDIR}/*.deb
> + fi
> }
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2024-06-26 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 11:05 Felix Moessbauer
2024-06-26 13:22 ` MOESSBAUER, Felix [this message]
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=1b58f74001e7ecb5fe027a3ce5929fb7fcfce287.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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