From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Cirujano Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Automatically add 'apt-transport-https' if any HTTPS mirror being used
Date: Tue, 27 Nov 2018 16:07:34 +0100 [thread overview]
Message-ID: <20181127160734.389ab1d8@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <1543322271.28585.13.camel@siemens.com>
Am Tue, 27 Nov 2018 12:37:53 +0000
schrieb "[ext] Cirujano Cuesta, Silvano"
<silvano.cirujano-cuesta@siemens.com>:
> IMHO ISAR should automatically install 'apt-transport-https' during
> debootstrapping if any of the provided mirrors uses HTTPS. Let me
> elaborate my reasons.
>
> There are two possible scenarios WRT Debian repositories involving
> HTTPS:
>
> 1. First mirror uses HTTPS
> 2. First mirror uses HTTP
>
> 1. works transparently with debootstrap > 1.0.58 (see [1]), since
> 'apt- transport-https' gets automatically added to the packages to
> install if the mirror to use (the first one) uses HTTPS.
>
> 2. WON'T WORK out of the box, since debootstrap won't install 'apt-
> transport-https' automatically (remember that it only uses the first
> one and it's not HTTPS). And therefore 'apt-transport-https' isn't
> available for installations from other mirrors (some of them being
> HTTPS).
>
> Fixing this limitation is not very difficult, but implies overriding
> 'isar-bootstrap.inc' just to add 'apt-transport-https' to the list of
> packages to be installed by debootstrap [2]. That's not convenient,
> and kind of overkilling.
>
> Letting ISAR handle it automatically is the solution I'd prefer, since
> it's very convenient and elegant and I don't see any drawbacks.
>
> In case I've overseen any drawbacks, then having the possibility of
> specifying additional packages to be installed during bootstrapping
> with a variable would be much better than overriding 'isar-
> bootstrap.inc'.
>
> Any opinions about it?
Sound like a good idea, will you send a patch?
Henning
> Regards,
> Silvano
>
> [1]
> https://sources.debian.org/src/debootstrap/1.0.110/debian/changelog/?hl
> =669#L669
>
> [2]
> https://github.com/ilbers/isar/blob/6c5db020b9b837d7b0ce63bfc719f9192e7
> 25f26/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc#L186
>
next prev parent reply other threads:[~2018-11-27 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 12:37 Cirujano Cuesta, Silvano
2018-11-27 15:07 ` Henning Schild [this message]
2018-11-27 15:40 ` Cirujano Cuesta, Silvano
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=20181127160734.389ab1d8@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=silvano.cirujano-cuesta@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