public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Andreas Reichel <andreas.reichel.ext@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
	Alexander Smirnov <asmirnov@ilbers.de>,
	"Maxim Yu. Osipov" <mosipov@ilbers.de>
Subject: Re: local apt repo cache not working as documented
Date: Mon, 26 Nov 2018 11:31:02 +0100	[thread overview]
Message-ID: <20181126113102.3a17b530@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20181126101027.GA1417@iiotirae>

Am Mon, 26 Nov 2018 11:10:27 +0100
schrieb Andreas Reichel <andreas.reichel.ext@siemens.com>:

> On Mon, Nov 26, 2018 at 10:55:20AM +0100, 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".
> > 
> > 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?
> >   
> 
> Interesting. I used commit SHA 60db83cdca, Jan Kiszka, Mon Nov 5
> directly on the next branch.

I will try with this. Shortly after that we have "d40a9ac093c24", which
probably causes the problem we see in current next.
I guess in case we use the cache we should call debootstrap with the
arg to ignore gpg.

Henning

> It worked as described in the user_manual.md
> 
> However: I only built the following 4 images:
> 
> multiconfig:qemuarm-stretch:isar-image-base
> multiconfig:qemuarm64-stretch:isar-image-base
> multiconfig:qemuamd64-stretch:isar-image-base
> multiconfig:bananapi-stretch:isar-image-base
> 
> I could rebuild these offline without problems.
> 
> I did not use any merged master branch or commits after that.
> 
> Andreas
> 
> > Henning  
> 


  reply	other threads:[~2018-11-26 10:31 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 [this message]
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

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=20181126113102.3a17b530@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