From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: Development branch updates
Date: Thu, 29 Jun 2017 16:33:07 +0200 [thread overview]
Message-ID: <71b64d59-76df-61cb-b931-96bee98ce543@siemens.com> (raw)
In-Reply-To: <20170628210313.GA3941@yssyq.radix50.net>
On 2017-06-28 23:03, Baurzhan Ismagulov wrote:
> Hello,
>
> I've updated the following branches for the latest stretch updates:
>
> master
> lenormf/uefi_wic_amd64-20170428
> lenormf/develop-l20170602-dpkg-cross
Thanks!
>
> multiconfig:qemuamd64:isar-image-base is buildable again.
qemu-amd64
BTW, the machine seems to be QEMU-agnostic -> rename to generic-amd64 or so?
>
> I'll be cherry-picking amd64, stretch and UEFI from
> lenormf/develop-l20170602-dpkg-cross into master.
This seems to work fine for Internet. Proxies are biting us here (as
usual), but this topic is bigger: I tried to pass http_proxy env down to
multistrap, but there are still many places where it gets lost.
What I noticed is that I cannot overwrite DISTRO_APT_SOURCE in
local.conf with a local mirror because of
DISTRO_APT_SOURCE = "..."
Any reason why we should not make them all
DISTRO_APT_SOURCE ??= "..."
? Or is the plan rather to allow setting a set of mirrors and let the
machinery pull from them when available, without local.conf overwrites?
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-06-29 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 21:03 Baurzhan Ismagulov
2017-06-29 14:33 ` Jan Kiszka [this message]
2017-06-29 20:47 ` Baurzhan Ismagulov
2017-06-30 7:26 ` Jan Kiszka
2017-07-04 10:11 ` Henning Schild
2017-06-29 23:28 ` Baurzhan Ismagulov
2017-06-30 7:27 ` Jan Kiszka
2017-07-06 22:06 ` Baurzhan Ismagulov
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=71b64d59-76df-61cb-b931-96bee98ce543@siemens.com \
--to=jan.kiszka@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