public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] sbuild: explain dependency issues with apt
Date: Thu, 25 May 2023 18:22:27 +0200	[thread overview]
Message-ID: <ef17d55e-56ae-f61f-4698-129b23f52832@siemens.com> (raw)
In-Reply-To: <20230525101026.605030-1-felix.moessbauer@siemens.com>

On 25.05.23 12:10, 'Felix Moessbauer' via isar-users wrote:
> This patch switches the sbuild uninstallable explainer tool from dose3
> to apt. Dose3 creates way too much output which often overflows the
> calling shells buffer. Also, the explanation sometimes is different,
> as we use apt as dependency resolver. To fix this, we simply switch to
> apt as explainer.

Great stuff!

Jan

> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  meta/classes/dpkg.bbclass | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index 5c8996d6..c596adbf 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -104,6 +104,7 @@ dpkg_runbuild() {
>      sbuild -A -n -c ${SBUILD_CHROOT} --extra-repository="${ISAR_APT_REPO}" \
>          --host=${PACKAGE_ARCH} --build=${BUILD_HOST_ARCH} ${profiles} \
>          --no-run-lintian --no-run-piuparts --no-run-autopkgtest --resolve-alternatives \
> +        --bd-uninstallable-explainer=apt \
>          --no-apt-update \
>          --chroot-setup-commands="echo \"Package: *\nPin: release n=${DEBDISTRONAME}\nPin-Priority: 1000\" > /etc/apt/preferences.d/isar-apt" \
>          --chroot-setup-commands="echo \"APT::Get::allow-downgrades 1;\" > /etc/apt/apt.conf.d/50isar-apt" \

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2023-05-25 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 10:10 Felix Moessbauer
2023-05-25 16:22 ` Jan Kiszka [this message]
2023-05-31  8:10 ` Uladzimir Bely

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=ef17d55e-56ae-f61f-4698-129b23f52832@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=felix.moessbauer@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