public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Jan Kiszka <jan.kiszka@web.de>, isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] buildchroot: Allow downgrades when installing packages
Date: Mon, 4 Mar 2019 10:04:01 +0100	[thread overview]
Message-ID: <c91bfe2b-e84f-f6f0-2d2a-a24c306e0212@siemens.com> (raw)
In-Reply-To: <88c264fd-db0f-55cc-ce5e-f19c11a45320@web.de>

Hi Jan,

On 23/02/2019 11.44, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> This can happen when changing the recipe of a self-built package, and
> that already when going from v1.0-rc3 to v1.0.

So the issue is that the buildchroot is reused for each recipe/package 
and if a newer one was once installed, it will not be removed. Right?

Then why not use a copy of the buildchroot for each recipe?

That way missing dependencies would also be found more easily.

regards,
Claudius

> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>   meta/classes/image.bbclass                      | 2 +-
>   meta/recipes-devtools/buildchroot/files/deps.sh | 4 +++-
>   2 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 3f4b728..574fb46 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -209,7 +209,7 @@ do_install_imager_deps() {
>               -o Dir::Etc::sourceparts="-" \
>               -o APT::Get::List-Cleanup="0"
>           apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y \
> -            --allow-unauthenticated install \
> +            --allow-unauthenticated --allow-downgrades install \
>               ${IMAGER_INSTALL}'
>   }
> 
> diff --git a/meta/recipes-devtools/buildchroot/files/deps.sh b/meta/recipes-devtools/buildchroot/files/deps.sh
> index 2501f05..1963943 100644
> --- a/meta/recipes-devtools/buildchroot/files/deps.sh
> +++ b/meta/recipes-devtools/buildchroot/files/deps.sh
> @@ -10,7 +10,9 @@ source /isar/common.sh
>   # Notes:
>   #   1) everything before the -y switch is unchanged from the defaults
>   #   2) we add -y to go non-interactive
> -install_cmd="apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y"
> +#   3) downgrades shall be allowed in case a package recipe was changed
> +install_cmd="apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends \
> +    -y --allow-downgrades"
> 
>   # Make sure that we have latest isar-apt content.
>   # Options meaning:
> --
> 2.16.4
> 

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  parent reply	other threads:[~2019-03-04  9:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 10:44 Jan Kiszka
2019-02-25  9:39 ` Henning Schild
2019-02-25  9:57   ` Jan Kiszka
2019-02-25 10:15     ` Henning Schild
2019-02-25 11:08       ` Jan Kiszka
2019-03-19 10:10         ` Baurzhan Ismagulov
2019-03-19 10:31           ` Jan Kiszka
2019-03-19 17:33             ` Maxim Yu. Osipov
2019-03-19 18:46               ` Jan Kiszka
2019-03-04  9:04 ` Claudius Heine [this message]
2019-03-04  9:08   ` Jan Kiszka
2019-03-28 12:42 ` Maxim Yu. Osipov

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=c91bfe2b-e84f-f6f0-2d2a-a24c306e0212@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@web.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