public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
	"[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
Cc: isar-users@googlegroups.com, "Kiszka,
	Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v3 5/6] Use all source lists in target root apt
Date: Thu, 07 Mar 2019 10:36:17 +0100	[thread overview]
Message-ID: <a36121029209b4d8e8bc18444db7fa948e3dfb05.camel@siemens.com> (raw)
In-Reply-To: <20190306182754.7cb25c81@md1za8fc.ad001.siemens.net>

Hi,

On Wed, 2019-03-06 at 18:27 +0100, [ext] Henning Schild wrote:
> Am Wed, 6 Mar 2019 17:26:17 +0100
> schrieb "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>:
> 
> > From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> > 
> > When we only use isar-apt.list, we cannot add additional
> > repositories
> > since they are listed in the bootstrap list only.
> 
> As far as i understood some entries in the list are not "enabled" or
> fully working before we added the key. The reasoning behind this
> change
> is somehow gpg ... and that needs to go in here. Because that is the
> first violation of "we only update isar-apt". But the violation is so
> early in the bootstrap that it is probably ok.

I don't think so. That apt-get update is part of the isar-bootstrap-
helper, so it will be called late when the image is build. That could
cause conflicting versions between the buildchroot and the resulting
image.

The reason why the general apt-get update is called only in the isar-
bootstrap recipe is so that there are no index conflicts between all
images that base itself on the same isar-bootstrap rootfs.

Claudius

> 
> Henning
> 
> > Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
> > ---
> >  meta/classes/isar-bootstrap-helper.bbclass | 5 +----
> >  1 file changed, 1 insertion(+), 4 deletions(-)
> > 
> > diff --git a/meta/classes/isar-bootstrap-helper.bbclass
> > b/meta/classes/isar-bootstrap-helper.bbclass index 1f24037..f9e3fba
> > 100644 --- a/meta/classes/isar-bootstrap-helper.bbclass
> > +++ b/meta/classes/isar-bootstrap-helper.bbclass
> > @@ -130,10 +130,7 @@ setup_root_file_system() {
> >              rm "$ROOTFSDIR/tmp/$kfn"
> >          done
> >      fi
> > -    sudo -E chroot "$ROOTFSDIR" /usr/bin/apt-get update \
> > -        -o Dir::Etc::sourcelist="sources.list.d/isar-apt.list" \
> > -        -o Dir::Etc::sourceparts="-" \
> > -        -o APT::Get::List-Cleanup="0"
> > +    sudo -E chroot "$ROOTFSDIR" /usr/bin/apt-get update
> >      # Add multiarch for cross-target
> >      if [ "${ROOTFS_ARCH}" != "${DISTRO_ARCH}" ]; then
> >          sudo -E chroot "$ROOTFSDIR" /usr/bin/dpkg --add-
> > architecture
> > ${DISTRO_ARCH}


  reply	other threads:[~2019-03-07  9:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 16:26 [PATCH v3 0/6] Fixes usage of additional apt keys and repos Andreas J. Reichel
2019-03-06 16:26 ` [PATCH v3 1/6] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-06 17:18   ` Henning Schild
2019-03-07  9:15     ` Andreas Reichel
2019-03-06 16:26 ` [PATCH v3 2/6] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-06 16:26 ` [PATCH v3 3/6] Fix key filename in apt-keyring generator Andreas J. Reichel
2019-03-06 16:26 ` [PATCH v3 4/6] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-06 17:33   ` Henning Schild
2019-03-07  9:06     ` Andreas Reichel
2019-03-07 13:43       ` Henning Schild
2019-03-06 16:26 ` [PATCH v3 5/6] Use all source lists in target root apt Andreas J. Reichel
2019-03-06 17:27   ` Henning Schild
2019-03-07  9:36     ` Claudius Heine [this message]
2019-03-06 16:26 ` [PATCH v3 6/6] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-06 17:43   ` Henning Schild
2019-03-07  9:14     ` Andreas Reichel
2019-03-07 13:41       ` Henning Schild
2019-03-07 14:41       ` Henning Schild

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=a36121029209b4d8e8bc18444db7fa948e3dfb05.camel@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=andreas.reichel.ext@siemens.com \
    --cc=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