public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH 5/5] build.sh: Force 'yes' for apt
Date: Mon,  5 Feb 2018 12:59:31 +0300	[thread overview]
Message-ID: <20180205095931.23903-6-asmirnov@ilbers.de> (raw)
In-Reply-To: <20180205095931.23903-1-asmirnov@ilbers.de>

Sometimes the following error occurs with custom repo:

After this operation, 84.0 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  libhello libhello-dev
E: There are problems and -y was used without --force-yes

This patch adds '--force-yes' option to be sure that no dialog will occur.

Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
---
 meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh
index b63a27e..06df1da 100644
--- a/meta/recipes-devtools/buildchroot/files/build.sh
+++ b/meta/recipes-devtools/buildchroot/files/build.sh
@@ -21,7 +21,7 @@ cd $1
 # 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"
+install_cmd="apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y --force-yes"
 
 # Install all build deps
 mk-build-deps -t "${install_cmd}" -i -r debian/control
-- 
2.1.4


  parent reply	other threads:[~2018-02-05 10:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  9:59 [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-05  9:59 ` [PATCH 1/5] Update isar-bitbake.conf according to the changes in bitbake related to multiconfig support Alexander Smirnov
2018-02-05 10:15   ` Jan Kiszka
2018-02-05 10:26     ` Alexander Smirnov
2018-02-05 10:27       ` Jan Kiszka
2018-02-05  9:59 ` [PATCH 2/5] isar-apt: Introduce separate recipe Alexander Smirnov
2018-02-05  9:59 ` [PATCH 3/5] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-05 10:18   ` Jan Kiszka
2018-02-05 10:33     ` Alexander Smirnov
2018-02-05  9:59 ` [PATCH 4/5] build.sh: Update apt sources Alexander Smirnov
2018-02-05  9:59 ` Alexander Smirnov [this message]
2018-02-05 11:52   ` [PATCH 5/5] build.sh: Force 'yes' for apt Jan Kiszka
2018-02-05 13:56     ` Alexander Smirnov
2018-02-05 13:48 ` [PATCH 3/5 v2] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-06 11:01   ` [PATCH 3/5 v3] " Alexander Smirnov
2018-02-06 12:10     ` Jan Kiszka
2018-02-06 13:28       ` Alexander Smirnov
2018-02-05 14:41 ` [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-05 16:47   ` Jan Kiszka
2018-02-05 16:56     ` Alexander Smirnov
2018-02-06 13:57 ` [PATCH 3/5 v4] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-06 17:31   ` Jan Kiszka
2018-02-06 18:29     ` Alexander Smirnov
2018-02-06 18:31       ` Jan Kiszka
2018-02-08 14:37   ` Henning Schild
2018-02-08 14:57     ` Alexander Smirnov
2018-02-06 20:24 ` [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-08 14:59 ` Henning Schild
2018-02-08 15:09   ` Jan Kiszka
2018-02-09 10:30     ` Henning Schild
2018-02-08 17:03   ` Benedikt Niedermayr
2018-02-08 18:27     ` Benedikt Niedermayr

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=20180205095931.23903-6-asmirnov@ilbers.de \
    --to=asmirnov@ilbers.de \
    --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