From: Jan Kiszka <jan.kiszka@siemens.com>
To: Maksim Osipov <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>,
Claudius Heine <ch@denx.de>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Reason why switching ISAR_USE_CACHED_BASE_REPO breaks
Date: Thu, 29 Nov 2018 17:53:33 +0100 [thread overview]
Message-ID: <cfb53214-c66c-ee26-2f5e-976634a77e2f@siemens.com> (raw)
Hi Maksim,
I bet one (if not the) reason why we cannot switch between
ISAR_USE_CACHED_BASE_REPO on and off for the same build output is that the
chroots always have the wrong apt sources configured.
That strongly suggests that we want to get rid of hard-coding base-apt into the
chroots because it breaks too many things (like apt on the target). We should
rather switch it managing those URLs dynamically, either from the outside
(proxies) or via temporarily applied rules that are reverted after each task so
that we can restart with arbitrary settings at any point.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
reply other threads:[~2018-11-29 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cfb53214-c66c-ee26-2f5e-976634a77e2f@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.de \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.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