public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: Andreas Reichel <Andreas.Reichel@tngtech.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] isar-bootstrap: Do not require https-support with custom bootstrap keys
Date: Mon, 12 Aug 2019 11:09:52 +0200	[thread overview]
Message-ID: <20190812090952.GA11083@yssyq.m.ilbers.de> (raw)
In-Reply-To: <caf2186d-15eb-ec5c-b166-2f0aa25c4452@siemens.com>

Hello Andreas,

On Fri, Aug 09, 2019 at 01:33:15PM +0200, Jan Kiszka wrote:
> There is apparently no problem to solve here, custom repos with custom
> keyrings build fine without https-support by debootstrap.
...
> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> @@ -163,13 +163,6 @@ def get_distro_have_https_source(d, is_host=False):
>      return any(source[2].startswith("https://") for source in generate_distro_sources(d, is_host))
>  
>  def get_distro_needs_https_support(d, is_host=False):
> -    distro_bootstrap_keys = d.getVar("DISTRO_BOOTSTRAP_KEYS", False)
> -    if distro_bootstrap_keys and distro_bootstrap_keys != "":
> -        # debootstrap falls back to https if there is no
> -        # 'reliable' keyring, whatever that means, but it happened
> -        # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891009
> -        return "https-support"
> -

Could you please comment on the motivation? What was your test case?

With kind regards,
Baurzhan.

  reply	other threads:[~2019-08-12  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 11:33 Jan Kiszka
2019-08-12  9:09 ` Baurzhan Ismagulov [this message]
2019-08-12  9:24   ` Andreas Reichel
2019-08-13 14:06     ` Henning Schild
2019-08-19  8:31 ` 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=20190812090952.GA11083@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --cc=Andreas.Reichel@tngtech.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