public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] buildchroot: Allow downgrades when installing packages
Date: Mon, 25 Feb 2019 10:39:35 +0100	[thread overview]
Message-ID: <20190225103935.489a466e@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <88c264fd-db0f-55cc-ce5e-f19c11a45320@web.de>

Am Sat, 23 Feb 2019 11:44:21 +0100
schrieb Jan Kiszka <jan.kiszka@web.de>:

> 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.

Seems pretty risky. If the only motivation is a local package, i would
argue your layer has a bug because it is going "up and down". If it
somehow needs to ... go ahead and do a complete rebuild.
But i guess we are talking about a multiconfig story again ...
I am against this one, we should rather move to the "clean-room" builds

Henning

> 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
> 


  reply	other threads:[~2019-02-25  9:39 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 [this message]
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
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=20190225103935.489a466e@md1za8fc.ad001.siemens.net \
    --to=henning.schild@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