From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6626668631260397568 X-Received: by 2002:a1c:2d12:: with SMTP id t18mr1671918wmt.9.1542896889619; Thu, 22 Nov 2018 06:28:09 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:4e4a:: with SMTP id r10ls169042wrt.15.gmail; Thu, 22 Nov 2018 06:28:09 -0800 (PST) X-Google-Smtp-Source: AFSGD/UpzYMzexSWeKAq67l8z83SyDQDag9F04j0gKKlXWMRjHfDtg+7WKKNODzoZXBP+D1Ryn9g X-Received: by 2002:adf:e948:: with SMTP id m8-v6mr1585883wrn.6.1542896889048; Thu, 22 Nov 2018 06:28:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542896889; cv=none; d=google.com; s=arc-20160816; b=Iy0pBowrHGaoIdclrw28QResXbfE8m0nxF6Tqlw13YVqdp5aZZXILKTmpLWUIX0O8e L/j69dlJ1bRzxIxIKVrtVeS0wQg52RcfYLE8JrOyHNfdI1ax3P8lV4fQBrHONlboqiGo 4GQn92PTwOMAOHMaGuNnEGZbvzMBcoOTJ3g9dt644tntOj7kyrc5wQt5xsHcwVPrMt26 lqohFW/iDEOLXojYUxNp/9HuyRSSl4Oq4URDp1EAoSm+4yhTKFQyFgSkePhV3pkJZtDe l8TNWQx/R69REtpqNG5giznGbxP9ovlbBRWOYPfaFk644kBwTuqss9nfFQpm9FLiyMMx iTEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=We4JW3Aw6QT9C1heBsRabhEp/YURYbxHU4ktw0gc69E=; b=yTsS0fdL18oTyeOwQxI+FOl+HhS0deIoLnzRzj1mHhOQN3XLwPTmYRVLYyNkNDspBf XwaLAXsL+0hNSvqdeZ+7myvYxKzvd5pAwcpHco5qb5qZMG2Qx4rDSk51wfKIbE80CbNZ 7N8hYp0XKCxM8jY0m8WSzL3Zlk4Sl1Dj6i9mywYtNMUJw7tpz2QW/RLzJCstZCrONk8M lu5HSyIejKIY6Qx5r1UUUpgazzNK79CFQIjs1yM2EVjV2p81yH8lzZKsNdhBHnY+9wh0 B8RH7/NuvU0BEEavMoJGBh3SDl8gwwS3zb+k6bT8HatMQ4xee3N/LiJ85yegBV/xdjAs 9ikQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id l4-v6si1598203wrb.4.2018.11.22.06.28.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Nov 2018 06:28:09 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id wAMES8Yo003196 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 22 Nov 2018 15:28:08 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id wAMES8FR017263; Thu, 22 Nov 2018 15:28:08 +0100 Subject: Re: [PATCH 1/3] bitbake: Update to fixed master revision To: Henning Schild Cc: isar-users 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> From: Jan Kiszka Message-ID: <3222ef02-53d9-30b0-4121-f20888a69e75@siemens.com> Date: Thu, 22 Nov 2018 15:28:06 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20181122145809.7181d469@md1za8fc.ad001.siemens.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: jaObn70HKXxZ 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. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux