From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6626668631260397568 X-Received: by 2002:a2e:9119:: with SMTP id m25-v6mr1074562ljg.22.1542901025339; Thu, 22 Nov 2018 07:37:05 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:7b01:: with SMTP id w1ls905312lfc.9.gmail; Thu, 22 Nov 2018 07:37:04 -0800 (PST) X-Google-Smtp-Source: AJdET5fTdzyvZjFvBzo7DPWcwUf1jvxym/ViSuKiw+rBxM8tMfIcyxlgD150bEl9iqu18/bDkdjV X-Received: by 2002:a19:740a:: with SMTP id v10mr969493lfe.16.1542901024863; Thu, 22 Nov 2018 07:37:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542901024; cv=none; d=google.com; s=arc-20160816; b=cr60o4DXyo8mLeElNdB6RwdsEkfapZ6zlFRij/v0vVTPv+SObQENZFsO0muNeOy1z6 GM5Fb8EwjHQJXRcTKsg5w83nv/OwTt8aaABPSC9R6+azpEuZ6+hMWFItN9WeXtgm24QA o9R7df4Riam0tYD2k5EYQcLDZ4MwWxiG4Vutr+KYxwnVG74kKJWq9KEA1J7W3pZpprNQ 2fxusYjE18du1EDaVribqeAYd1oflQhnPoIxh1C+5qHKz6jRS/EqQRbvrtt0snqIb6tC Deh8E/pmpWz1gQhQEF4Xqq4LMXiTYz227E6il+uOXxRi2OXogGuMNuiiICW9T7/pAbJB eMHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=zw4lF0wWGq3jBHLk2mpXOJ8J8Sp2aa0C3WZYoDmaOaU=; b=l97ZqznuMTW/2TkgDjoJ9nfm1bEqORHCbLYpuGIVI1TleyJlI6FvT96M8tld2kk4AF Ftev0f2ptvD3GDeknmclrj+ARzoxIRgB5ymdWFNpbB7buL+J86rr1uPrr7DCc1JK491V snfdEvwK0yOFgiwV8HnDe5z362lvY2BloSc+8tbXI3/BvNcunv3D0bOVtEhdd/C/mFz7 Uqqbe5BPPY7+/aNoJ0RkcfvUQZwilWzCDoduFxjNZ72dMZk/8gNVWYoIGkULIsjkkslW 5tAWetI0AzEeR9AlcIpyIXjOluDSyz4zygExZTtbnhFZdwqth+EdooZtIVc0csVrRiGJ QrOQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id n189si915997lfa.4.2018.11.22.07.37.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Nov 2018 07:37:04 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id wAMFb31e003708 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 22 Nov 2018 16:37:04 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.69.187]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id wAMFb3bV023916; Thu, 22 Nov 2018 16:37:03 +0100 Date: Thu, 22 Nov 2018 16:36:53 +0100 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: [PATCH 1/3] bitbake: Update to fixed master revision Message-ID: <20181122163653.1634313f@md1za8fc.ad001.siemens.net> In-Reply-To: <3222ef02-53d9-30b0-4121-f20888a69e75@siemens.com> References: <378881f38c00958d2f388c9c7e5a7f1df8efebd2.1542891520.git.jan.kiszka@siemens.com> <20181122141229.60d1830c@md1za8fc.ad001.siemens.net> <813c05e6-d680-6ac3-ff1f-41165a908c9f@siemens.com> <20181122141847.48b326a4@md1za8fc.ad001.siemens.net> <067a2c58-179e-6948-b815-07368a3b44f8@siemens.com> <20181122145809.7181d469@md1za8fc.ad001.siemens.net> <3222ef02-53d9-30b0-4121-f20888a69e75@siemens.com> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: 4XY+Kb/3NfU9 Am Thu, 22 Nov 2018 15:28:06 +0100 schrieb Jan Kiszka : > On 22.11.18 14:58, Henning Schild wrote: > > Am Thu, 22 Nov 2018 14:25:25 +0100 > > schrieb Jan Kiszka : > > > >> On 22.11.18 14:18, Henning Schild wrote: > >>> Am Thu, 22 Nov 2018 14:14:11 +0100 > >>> schrieb Jan Kiszka : > >>> > >>>> On 22.11.18 14:12, Henning Schild wrote: > >>>>> I got a report that bitbake 1.40 and this one are affected by a > >>>>> "gitsm://" bug. Still waiting for details but this will only fix > >>>>> one new bitbake bug. > >>>>> Was there a reason to bump, except wanting to stay up to date? > >>>> > >>>> Broken multiconfig in current next. So far a downstream issue > >>>> (jailhouse-images, possibly other multiconfig-using layers), with > >>>> patch 3 then also an upstream topic. But patch 3 is needed for > >>>> other reasons (see log). > >>> > >>> Is that the answer to 1.37->1.40 or just 1.40 -> this ? > >>> > >> > >> The step 1.37->1.40 caused the multiconfig problem > >> (http://lists.openembedded.org/pipermail/bitbake-devel/2018-November/019558.html) > >> that is now fixed with this update again. > > > > I got that, i was already thinking about going back to 1.37 ... > > maybe. > > Well, if we cannot sort out the gitsm issue AND it is blocking for > you, I would consider that. gitsm thing is known upstream and we can work around it by adjusting out .gitmodules, bet seems we need one of the changes this patch includes. So i guess it is solved and we want this one merged fast ;). http://lists.openembedded.org/pipermail/bitbake-devel/2018-November/019532.html Henning > Jan >