From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6723128764544319488 X-Received: by 2002:a1c:4803:: with SMTP id v3mr26749711wma.49.1565601001767; Mon, 12 Aug 2019 02:10:01 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:a557:: with SMTP id o84ls4407185wme.3.gmail; Mon, 12 Aug 2019 02:10:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqypnsuSXb6cFvmM6zvCEz8mTRtGXeltIE/4wFD80eS854oWrfG63aJMfk6kPk8lokHlPTKO X-Received: by 2002:a7b:cf21:: with SMTP id m1mr28033518wmg.150.1565601001346; Mon, 12 Aug 2019 02:10:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565601001; cv=none; d=google.com; s=arc-20160816; b=VyAAzZo/oH0kYQgpxBeqdwmkrQ906XWKd2M1Vk0fl8ixIoz9RyZrOzGp07ntNtG9Ix kiThltK0NknhQXL4kiQs3LsMIEz8+ExDeM9q4uFV94UaLGkzb780M/jPS81FDoMjyoSr ENRQH2pTR0tC56P1cJeyD1ECKnmYWE1fxbK2QfalH8Rt/mTwQdfZAZURlJ7mGs6EUmvZ Bg9WcdbqmuGSI98ON/ibxCK2SBzk6QzeQnNgucOxBT57UyHrbKb+vBLK3pdI4J75QCBh 1qGnfqgKQdLYsO1ZeE6PSw8UhPfpghnzEEYG5rNJWJ1ZhQIabEGNboXY5Zdwp5gYDGsj VbnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date; bh=aquwgvrB89e/Yv5jE19pcAecJnt8e4CRU2TyPHjGKEM=; b=CaSicEuAOQ2xdirWgF0shIQM4/zfX36DESC5tV17/+GXxLqEk/x9rUNFdFiUSIMhOJ YfyUdH4yWvoN9ckCNSI+FfscYdE22tB9g3NjOkkjPBtj+DMeEdiZeH2sYgvea4Eh0koK dGufF2Itu51gHcnOFcVQ/RMqHCsyo8+hEs8b1KTPnqRpoGxglCwUYo7p/th9u9VruurA OW1V/oB5su5uWv2E+8SwyTdyZ0P/lq0pLi9InWxp8L8J/1UH8nMGGPFMC/SKI0BqeamE u1w8FV/Uo/wm8OoK7mvCUX/2km7VpNLARu+lc9WuCQWfBlCrBV/4Ak4JSqVWmGOMF1pt DevQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id e7si563019wru.1.2019.08.12.02.10.01 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 12 Aug 2019 02:10:01 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x7C99qZx007547 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Aug 2019 11:10:00 +0200 Date: Mon, 12 Aug 2019 11:09:52 +0200 From: Baurzhan Ismagulov To: Andreas Reichel Cc: isar-users Subject: Re: [PATCH] isar-bootstrap: Do not require https-support with custom bootstrap keys Message-ID: <20190812090952.GA11083@yssyq.m.ilbers.de> Mail-Followup-To: Andreas Reichel , isar-users References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: BADixZulL/d9 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.