From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 1/6] linux-custom: Add missing proxy settings to prepare task
Date: Sun, 2 Sep 2018 18:04:35 +0200 [thread overview]
Message-ID: <29a6df5d734fa686fa543f88f592c99fe0eda0fe.1535904280.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1535904280.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1535904280.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Lost by a70dd2339cc7.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/recipes-kernel/linux/linux-custom.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index d75346e..57f2f82 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -29,6 +29,7 @@ KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, kmod, linux-ba
KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, libssl1.1"
dpkg_prepare() {
+ E="${@ bb.utils.export_proxies(d)}"
sudo -E chroot ${BUILDCHROOT_DIR} \
apt-get install \
-y -o Debug::pkgProblemResolver=yes \
--
2.16.4
next prev parent reply other threads:[~2018-09-02 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:04 [PATCH 0/6] dpkg class refactorings, API changelog, fixes Jan Kiszka
2018-09-02 16:04 ` Jan Kiszka [this message]
2018-09-02 16:04 ` [PATCH 2/6] linux-module: Run depmod for installed kernel versions Jan Kiszka
2018-09-02 16:04 ` [PATCH 3/6] dpkg-base: Relocate dpkg_runbuild and adjust comments Jan Kiszka
2018-09-02 16:04 ` [PATCH 4/6] dkpg-base: Clarify dependency logic between package recipes Jan Kiszka
2018-09-02 16:04 ` [PATCH 5/6] dpkg, linux-custom: Split dependency installation from build preparations Jan Kiszka
2018-09-02 16:04 ` [PATCH 6/6] Add changelog for the recipe API Jan Kiszka
2018-09-02 16:13 ` [PATCH 0/6] dpkg class refactorings, API changelog, fixes Jan Kiszka
2018-09-10 9:37 ` Maxim Yu. Osipov
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=29a6df5d734fa686fa543f88f592c99fe0eda0fe.1535904280.git.jan.kiszka@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