From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: local apt repo cache not working as documented
Date: Thu, 29 Nov 2018 11:40:56 +0100 [thread overview]
Message-ID: <20181129104056.GD17904@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20181128161359.40702b85@md1za8fc.ad001.siemens.net>
On Wed, Nov 28, 2018 at 04:13:59PM +0100, Henning Schild wrote:
> That is all already solved in Isar. You have DISTRO_APT_SOURCES where
> you select what should be used for installation and for delivery. The
> caching mechanism needs to change "installation" but there is no excuse
> to break "delivery".
The definition of "breaking" depends on whether upstream sources are required /
allowed in a particular product. But as discussed offline, it's convenient for
users, so we'll look at that.
> So yes, you need to undo the patching before do_image and get the user
> back to what they specified in DISTRO_APT_SOURCES.
Technically, it's actively patching the upstream URI into sources.list, since
it's created with the local URI by debootstrap.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2018-11-29 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 9:55 Henning Schild
2018-11-26 9:57 ` Jan Kiszka
2018-11-26 11:36 ` Hombourger, Cedric
2018-11-26 10:10 ` Andreas Reichel
2018-11-26 10:31 ` Henning Schild
2018-11-26 11:01 ` Maxim Yu. Osipov
2018-11-26 11:12 ` Henning Schild
2018-11-26 11:35 ` Maxim Yu. Osipov
2018-11-27 9:45 ` Henning Schild
2018-11-28 9:00 ` Baurzhan Ismagulov
2018-11-28 9:04 ` Jan Kiszka
2018-11-28 15:13 ` Henning Schild
2018-11-29 10:40 ` Baurzhan Ismagulov [this message]
2018-11-28 19:48 ` 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=20181129104056.GD17904@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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