public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 4/5] dpkg: Account for changes in mk-build-deps in bullseye
Date: Thu, 24 Sep 2020 23:32:09 +0200	[thread overview]
Message-ID: <20200924233209.3c808a50@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <d5688a50474525c2ef1ad209a3f73ab42745dc89.1600962590.git.jan.kiszka@siemens.com>

On Thu, 24 Sep 2020 17:49:50 +0200
"[ext] Jan Kiszka" <jan.kiszka@siemens.com> wrote:

> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> In bullseye, mk-build-deps now emits two log files. When rebuilding
> debian packages, those files end up in ${S} and will be recognized by
> the package build as deviation from the source file. Avoid this
> failure by stepping out of ${S} before calling mk-build-deps.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  meta/recipes-devtools/buildchroot/files/deps.sh | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-devtools/buildchroot/files/deps.sh
> b/meta/recipes-devtools/buildchroot/files/deps.sh index
> 93bc9cf5..1d617bc8 100644 ---
> a/meta/recipes-devtools/buildchroot/files/deps.sh +++
> b/meta/recipes-devtools/buildchroot/files/deps.sh @@ -33,17 +33,20 @@
> if ! grep "^Architecture:" debian/control | grep -qv "all"; then
> set_arch="" fi
>  
> +control_file=$(pwd)/debian/control
> +cd ..

Would it be a good idea to make this absolute instead of relative? Or
maybe we can make mk-build-deps place those temporary files somewhere
else?

Changing the working directory somewhere inbetween can be pretty
confusing when extending later.

Henning

> +
>  # Install all build deps
>  if [ "$3" = "--download-only" ]; then
>      # this will not return 0 even when it worked
> -    mk-build-deps $set_arch -t "${install_cmd}" -i -r debian/control
> &> \
> +    mk-build-deps $set_arch -t "${install_cmd}" -i -r $control_file
> &> \ mk-build-deps.output || true
>      cat mk-build-deps.output
>      # we assume success when we find this
>      grep "mk-build-deps: Unable to install all build-dep packages"
> mk-build-deps.output rm -f mk-build-deps.output
>  else
> -    mk-build-deps $set_arch -t "${install_cmd}" -i -r debian/control
> +    mk-build-deps $set_arch -t "${install_cmd}" -i -r $control_file
>  
>      # Upgrade any already installed packages in case we are
> partially rebuilding apt-get upgrade -y --allow-downgrades


  reply	other threads:[~2020-09-24 21:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 15:49 [PATCH 0/5] More fixes and cleanups Jan Kiszka
2020-09-24 15:49 ` [PATCH 1/5] buildchroot-host: Drop unneeded :native for riscv64 setup Jan Kiszka
2020-09-24 15:49 ` [PATCH 2/5] deb-dl-dir: Fix quoting Jan Kiszka
2020-09-24 21:27   ` Henning Schild
2020-09-24 15:49 ` [PATCH 3/5] Fix dependencies on isar-apt Jan Kiszka
2020-09-24 15:49 ` [PATCH 4/5] dpkg: Account for changes in mk-build-deps in bullseye Jan Kiszka
2020-09-24 21:32   ` Henning Schild [this message]
2020-09-25  6:21     ` Jan Kiszka
2020-09-25  7:02       ` Henning Schild
2020-09-24 15:49 ` [PATCH 5/5] isar-bootstrap: Align debootstrap calls Jan Kiszka

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=20200924233209.3c808a50@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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