public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>,
	Henning Schild <henning.schild@siemens.com>
Subject: [PATCHv2 1/2] isar-apt: Mark repo as trusted in sources.list
Date: Thu, 24 May 2018 17:26:51 +0200	[thread overview]
Message-ID: <ade2a598fe5614aeacd24f7195b49df8aa0df92d.1527175529.git.henning.schild@siemens.com> (raw)

Mark our own repository 'isar-apt' trusted in sources.list, and then
drop the '--allow-unauthenticated' switch we used for apt-get so far.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 meta/classes/isar-bootstrap-helper.bbclass       | 5 ++---
 meta/recipes-devtools/buildchroot/files/build.sh | 3 ---
 2 files changed, 2 insertions(+), 6 deletions(-)

diff --git a/meta/classes/isar-bootstrap-helper.bbclass b/meta/classes/isar-bootstrap-helper.bbclass
index 4284d02..30f768c 100644
--- a/meta/classes/isar-bootstrap-helper.bbclass
+++ b/meta/classes/isar-bootstrap-helper.bbclass
@@ -11,15 +11,14 @@ setup_root_file_system() {
     shift
     shift
     PACKAGES="$@"
-    APT_ARGS="install --yes --allow-unauthenticated \
-              -o Debug::pkgProblemResolver=yes"
+    APT_ARGS="install --yes -o Debug::pkgProblemResolver=yes"
     CLEANHOSTLEAK_FILES="${ROOTFSDIR}/etc/hostname ${ROOTFSDIR}/etc/resolv.conf"
 
     sudo cp -Trpfx \
         "${DEPLOY_DIR_IMAGE}/isar-bootstrap-${DISTRO}-${DISTRO_ARCH}/" \
         "$ROOTFSDIR"
 
-    echo "deb file:///isar-apt ${DEBDISTRONAME} main" | \
+    echo "deb [trusted=yes] file:///isar-apt ${DEBDISTRONAME} main" | \
         sudo tee "$ROOTFSDIR/etc/apt/sources.list.d/isar-apt.list" >/dev/null
 
     echo "Package: *\nPin: release n=${DEBDISTRONAME}\nPin-Priority: 1000" | \
diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh
index aa769e4..73c0889 100644
--- a/meta/recipes-devtools/buildchroot/files/build.sh
+++ b/meta/recipes-devtools/buildchroot/files/build.sh
@@ -20,9 +20,6 @@ export LANGUAGE=C
 #   2) we add -y to go non-interactive
 install_cmd="apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y"
 
-# Allow unauthenticated feeds
-install_cmd="${install_cmd} --allow-unauthenticated"
-
 (
     # Lock-protected because apt and dpkg do not wait in case of contention
     flock 42 || exit 1
-- 
2.16.1


             reply	other threads:[~2018-05-24 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 15:26 Henning Schild [this message]
2018-05-24 15:26 ` [PATCHv2 2/2] conf: Add support for new debian distro "buster" Henning Schild
2018-05-27 19:54   ` Alexander Smirnov
2018-06-07  9:53     ` Maxim Yu. Osipov
2018-06-25 12:44     ` Henning Schild
2018-06-25 12:47     ` [PATCH v3] " Henning Schild
2018-07-13 11:13       ` Maxim Yu. Osipov
2018-07-13 12:36         ` Jan Kiszka
2018-05-24 15:31 ` [PATCHv2 1/2] isar-apt: Mark repo as trusted in sources.list Henning Schild
2018-06-01 15:52   ` 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=ade2a598fe5614aeacd24f7195b49df8aa0df92d.1527175529.git.henning.schild@siemens.com \
    --to=henning.schild@siemens.com \
    --cc=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