public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH v6 07/12] sbuild: support of shell exports from dpkg_runbuild_prepend
Date: Thu, 3 Mar 2022 13:36:30 +0000	[thread overview]
Message-ID: <AM9PR10MB48698F892FBA3A33D2C0405289049@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220210064620.4392-8-ubely@ilbers.de>

Hi,

> +
> +        # Don't warn some variables
> +        [ "${var}" = "PARALLEL_MAKE" ] && continue
> +        [ "${var}" = "CCACHE_DIR" ] && continue
> +        [ "${var}" = "PATH_PREPEND" ] && continue
> +        [ "${var}" = "DEB_BUILD_OPTIONS" ] && continue
> +        [ "${var}" = "DEB_BUILD_PROFILES" ] && continue
> +
> +        bbwarn "Export of '${line}' detected, please migrate to templates"

There are more variables that have to be excluded, e.g. all proxy related settings:
(http_proxy, HTTP_PROXY, https_proxy, HTTPS_PROXY, no_proxy, NO_PROXY).

But the proxy settings have to be passed into the sbuild environment.
Currently, building behind a proxy fails (in do_dpkg_build):

+------------------------------------------------------------------------------+
| Update chroot                                                                |
+------------------------------------------------------------------------------+
[...]
Err:8 http://deb.debian.org/debian bullseye Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:62::644). - connect (101: Network is unreachable)

Best regards,
Felix

--
Siemens AG, Technology, T CED SES-DE
Otto-Hahn-Ring 6, 81739 München, Germany



  reply	other threads:[~2022-03-03 13:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  6:46 [PATCH v6 00/12] Sbuild/Schroot migration Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 01/12] dpkg-gbp: Use separate command to export tarball Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 02/12] dpkg-gbp: Use host tools for dsc preparation Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 03/12] sbuild: Add recipes for host and target rootfs to run sbuild Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 04/12] sbuild: Introduce a class for another build method Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 05/12] dpkg: Build packages with sbuild Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 06/12] sbuild: support of DEB_BUILD_PROFILES Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 07/12] sbuild: support of shell exports from dpkg_runbuild_prepend Uladzimir Bely
2022-03-03 13:36   ` Moessbauer, Felix [this message]
2022-03-09 17:57     ` Moessbauer, Felix
2022-03-14 12:28       ` Uladzimir Bely
2022-03-14 14:52         ` Moessbauer, Felix
2022-02-10  6:46 ` [PATCH v6 08/12] dpkg: Remove builddeps install task Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 09/12] sbuild: add ccache support Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 10/12] dpkg-base: Switch devshell to use schroot Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 11/12] dpkg-base: Switch apt_fetch and apt_unpack " Uladzimir Bely
2022-02-10  6:46 ` [PATCH v6 12/12] doc: Add sbuild-related documentation Uladzimir Bely

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=AM9PR10MB48698F892FBA3A33D2C0405289049@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@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