public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, "Fong, Amy" <Amy_Fong@mentor.com>
Cc: "[ext] Henning Schild" <henning.schild@siemens.com>,
	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: Mon, 26 Nov 2018 11:36:22 +0000	[thread overview]
Message-ID: <39F6F59F-FFA7-4D4C-822E-CBA490F987DA@mentor.com> (raw)
In-Reply-To: <932ac7b3-5602-5c88-637b-90385afbe014@siemens.com>

Hi Jan

It does sound like. I am adding Amy to the thread. Amy, please “git send-email” your patch to isar-users@googlegroups.com (traveling to eastern regions today but should be online in the evening if you need me)

Thanks
Cedric

Sent from a mobile

> On 26 Nov 2018, at 10:57, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
>> On 26.11.18 10:55, [ext] 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?
> 
> Cedric, sounds like the issue you were discussing on Friday off-list.
> 
> Jan
> 
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux

  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 [this message]
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

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=39F6F59F-FFA7-4D4C-822E-CBA490F987DA@mentor.com \
    --to=cedric_hombourger@mentor.com \
    --cc=Amy_Fong@mentor.com \
    --cc=andreas.reichel.ext@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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