From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Alexander Smirnov <asmirnov@ilbers.de>,
Andreas Reichel <andreas.reichel.ext@siemens.com>
Subject: Re: local apt repo cache not working as documented
Date: Mon, 26 Nov 2018 14:35:46 +0300 [thread overview]
Message-ID: <ea3162b7-a38a-b1fb-26a6-24b76704b90a@ilbers.de> (raw)
In-Reply-To: <20181126121250.760fc6ee@md1za8fc.ad001.siemens.net>
On 11/26/18 2:12 PM, Henning Schild wrote:
> Am Mon, 26 Nov 2018 14:01:35 +0300
> schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
>
>> On 11/26/18 12:55 PM, Henning Schild wrote:
>>> 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".
>>
>> I've checked out 2997d073dc1a, followed instructions in
>> doc/user-manual.md for multiconfig:qemuarm-stretch:isar-image-base -
>> feature works.
>>
>> As for the current 'next' - I confirm that feature doesn't work. As
>> for a quick fix one may revert d40a9ac0, but proper fix would be
>> adding signing of local repo I'm currently busy with.
>
> And a CI test case. Did you disconnect from all networks when you
> succeeded with 2997d?
Yes, I disabled networking.
Maxim.
> Henning
>
>> Maxim.
>>
>>> 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
>>>
>>
>>
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-11-26 11:36 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 [this message]
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
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=ea3162b7-a38a-b1fb-26a6-24b76704b90a@ilbers.de \
--to=mosipov@ilbers.de \
--cc=andreas.reichel.ext@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=henning.schild@siemens.com \
--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