From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Alexander Smirnov <asmirnov@ilbers.de>,
"Maxim Yu. Osipov" <mosipov@ilbers.de>,
"Andreas Reichel" <andreas.reichel.ext@siemens.com>
Subject: Re: local apt repo cache not working as documented
Date: Wed, 28 Nov 2018 20:48:59 +0100 [thread overview]
Message-ID: <20181128204859.354d3f85@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20181126105520.03a0209b@md1za8fc.ad001.siemens.net>
Hi,
i was working on a more elegant solution than just the revert.
Basically something that would act on [trusted=yes] in the sources.list
and derive the debootstrap arg from that.
But turns out the [trusted=yes] enters the rootfs in another way than
debootstrap is tricked into using the other mirror.
Long story short, please apply the revert, the better solution will
have to wait.
Henning
Am Mon, 26 Nov 2018 10:55:20 +0100
schrieb "[ext] Henning Schild" <henning.schild@siemens.com>:
> Hi,
>
> i tried building an image from a local cache, just like the docs
> describe the process. On the second try debootstrap always complains
> about gpg issues. It does not work on current next and also did not
> work the day the feature was merged "2997d073dc1a".
>
> Yet another feature that got merged without a test-case ...
>
> @Andreas you are working with that, did you apply any local patches
> that should be sent upstream?
>
> Henning
>
prev parent reply other threads:[~2018-11-28 19:49 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
2018-11-28 19:48 ` Henning Schild [this message]
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=20181128204859.354d3f85@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=andreas.reichel.ext@siemens.com \
--cc=asmirnov@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