From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Q. Gylstorff" <Quirin.Gylstorff@siemens.com>
Cc: <isar-users@googlegroups.com>, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] isar-bootstrap: Remove apt-transport-https
Date: Tue, 10 Mar 2020 15:02:04 +0100 [thread overview]
Message-ID: <20200310150204.0f64916b@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20200228112943.13864-1-Quirin.Gylstorff@siemens.com>
Good catch but a serious user interface break you are suggesting here.
I would suggest a backward compatible solution. And if you do not find
one, a big fat entry in RECIPE-API-CHANGELOG.md
Henning
On Fri, 28 Feb 2020 12:29:43 +0100
"[ext] Q. Gylstorff" <Quirin.Gylstorff@siemens.com> wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> Since apt 1.5 apt-transport-https is part of apt[1]. This
> package is no longer needed. For https transport in
> a distribution older than Debian 10 (buster)
> append the Distro configuration with:
> DISTRO_BOOTSTRAP_BASE_PACKAGES_append = ",apt-transport-https"
>
> [1]: https://packages.debian.org/buster/apt-transport-https
>
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc index
> 16b4395..d1fbb81 100644 ---
> a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc +++
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc @@ -27,7 +27,7
> @@ THIRD_PARTY_APT_KEYFILES = "" DEPLOY_ISAR_BOOTSTRAP ?= ""
> DISTRO_BOOTSTRAP_BASE_PACKAGES = "locales"
> DISTRO_BOOTSTRAP_BASE_PACKAGES_append_gnupg = ",gnupg"
> -DISTRO_BOOTSTRAP_BASE_PACKAGES_append_https-support =
> ",apt-transport-https,ca-certificates"
> +DISTRO_BOOTSTRAP_BASE_PACKAGES_append_https-support =
> ",ca-certificates" HOST_DISTRO_APT_SOURCES +=
> "conf/distro/${HOST_DISTRO}.list" python () {
next prev parent reply other threads:[~2020-03-10 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 11:29 Q. Gylstorff
2020-03-10 14:02 ` Henning Schild [this message]
2020-03-10 16:07 ` [PATCH v2] " Q. Gylstorff
2020-03-10 22:09 ` Henning Schild
2020-03-11 13:51 ` Gylstorff Quirin
2020-03-11 13:51 ` Gylstorff Quirin
2020-03-11 13:57 ` [PATCH v3] " Q. Gylstorff
2020-04-06 5:57 ` 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=20200310150204.0f64916b@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Quirin.Gylstorff@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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