public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 1/5] dpkg: Make mount buildroot reliable
Date: Tue, 8 Jun 2021 10:49:15 +0200	[thread overview]
Message-ID: <20210608104915.78be4c3c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <317dd4d0-e1b7-50d1-39e3-0b9bd9fd2798@ilbers.de>

Am Tue, 8 Jun 2021 11:31:03 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:

> 08.06.2021 11:09, Henning Schild wrote:
> > Sure that the new pattern will make this shell have the variables?
> > Building behind proxies is unfortunately something we need. Could be
> > tried with BB_NO_NETWORK which should make you fail because of
> > deadend_proxy
> >
> > Henning  
> 
> This code was not removed but just moved from bash to python.
> So there is still check for SRC_APT and isar_export_proxy call there.
> Please look at meta/classes/dpkg-base.bbclass

I did see that it was moved. But shell functions in bitbake often open
a new shell and do not inherit all env, that is why we need to export
the variables all over the place instead of just doing it once. And i
am afraid doing in python and later forking a fresh shell might make
you not have the variables in the shell.

It should be double checked that shell functions opened with the
pattern of "isar_export_proxies; bb.build.exec_func" do receive the
variables as they used to. Maybe it is already the case, just asking
and pointing out.

Henning


  reply	other threads:[~2021-06-08  8:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08  6:25 [PATCH v3 0/5] Rebuild mount logic Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 1/5] dpkg: Make mount buildroot reliable Anton Mikanovich
2021-06-08  8:09   ` Henning Schild
2021-06-08  8:31     ` Anton Mikanovich
2021-06-08  8:49       ` Henning Schild [this message]
2021-07-01 11:55   ` Jan Kiszka
2021-05-08  6:25 ` [PATCH v3 2/5] buildchroot: Unmount buildchroot mounts if not needed Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 3/5] rootfs: Unmount rootfs " Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 4/5] wic: Unmount dirs after usage Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 5/5] events: Warn if mounted paths left Anton Mikanovich
2021-07-01 11:51   ` Jan Kiszka
2021-06-08  7:58 ` [PATCH v3 0/5] Rebuild mount logic Henning Schild
2021-06-08  8:15   ` Anton Mikanovich
2021-06-08  8:42     ` Henning Schild
2021-06-08  8:54     ` Henning Schild
2021-06-10  7:12       ` Anton Mikanovich
2021-06-10 15:02         ` Henning Schild
2021-06-21 15:54 ` Jan Kiszka
2021-06-22 14:40   ` Anton Mikanovich

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=20210608104915.78be4c3c@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --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