public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
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: Tue, 13 Aug 2019 16:06:36 +0200	[thread overview]
Message-ID: <20190813160636.7c056524@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190812092430.GA31772@archlinux>

Am Mon, 12 Aug 2019 11:24:30 +0200
schrieb Andreas Reichel <Andreas.Reichel@tngtech.com>:

> On Mon, Aug 12, 2019 at 11:09:52AM +0200, Baurzhan Ismagulov wrote:
> > 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?  
> 
> I am sorry, I cannot add more than I already wrote as comment. If you
> don't understand this bug neither (I didn't), and it does not happen
> again, maybe try without this. If it doesn't break then fine.

This fallback path should only be taken when debootstrap is not called
with a USER_MIRROR. And it seems we do not ever have that case in Isar.
Maybe the problem appeared in intermediate manual steps. Or with some
older version of debootstrap.

Henning

> Kind regards
> 
> > 
> > With kind regards,
> > Baurzhan.  
> 


  reply	other threads:[~2019-08-13 14:06 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
2019-08-12  9:24   ` Andreas Reichel
2019-08-13 14:06     ` Henning Schild [this message]
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=20190813160636.7c056524@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --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