From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6618191789727678464 X-Received: by 2002:a1c:b5cc:: with SMTP id e195-v6mr21492wmf.17.1541152510184; Fri, 02 Nov 2018 02:55:10 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:5081:: with SMTP id a1-v6ls3318002wrt.13.gmail; Fri, 02 Nov 2018 02:55:09 -0700 (PDT) X-Google-Smtp-Source: AJdET5fr3oO1LPJE6MFUJooHkQnGwgx7wSMq3n1uaQv0HZ/nbH58rl0Gj5tBhqrUkgfj7Xn/XV9k X-Received: by 2002:a5d:4349:: with SMTP id u9-v6mr1126290wrr.29.1541152509791; Fri, 02 Nov 2018 02:55:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541152509; cv=none; d=google.com; s=arc-20160816; b=TpP2927voKCFA/kioPmyXJJt8Duva3ImMxLRrv9j+5lWSNzfaL0imajCoTKjzgOkAM hvsuxzBH7fwoLz/Olt3Gjcm2+4vf3y1HbPXjaWNaVdbkEi5STSZwOJS2jp38cMg4wo6u dOJ1OCf53UULkAfwzGb9XO1caJ3S+G5TKRzgJOhqjJ1OpSvaReAttZ6AP8CnL3SxGbED +7KNqxuDHiAyYFFUVFornGJyErPivPB5U2onjh9t0QwojQdXwpuKUp8wWvsoyzUa7euM 7Mhykt/dM6jV5YebZIumAsrL2anq+BCvVhOFSfX5og1qdrHa5kU9M5PATE4Q9jDCsKVG U+Mg== 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=lCIJ5vjy3EY8VUnFTemMnqehJg+Emm5XsvRFD2h5cnU=; b=woLaGzf1M3MzFmzdvMPZdnzrFzhEZzYk7mUKDfq8pZPohZToR3IOH7vthjewfNNp7g FeV1+Yw+P9GHM1FFfFpl3sIgnU7PiYeH+SFOpQ42/Rr0Q+g7B4pM7jIUc1Uwjc1BuSUk hKn5ChuZvwDFGgFfYKD8MideACtQRplFLuCrh3whU15mLft+HJsXxHC4BwppHGMLR+GI xz4BcWUXxKznpQDIgrsCqMdykibh993G1U7L4zhq5TMAYHUVjrYiVbnBFp3mxwivO0Jd Ko+CmBUdainV8tMdPMOlnkfFJka/Rjsf8/P5w7rnMkjmYNoYHqtrzThiI2upjVZPLn7h gO+w== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id n6-v6si434580wrj.4.2018.11.02.02.55.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Nov 2018 02:55:09 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id wA29t9Mx020976 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 2 Nov 2018 10:55:09 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.68.199]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id wA29t9iI001648; Fri, 2 Nov 2018 10:55:09 +0100 Date: Fri, 2 Nov 2018 10:55:08 +0100 From: Henning Schild To: "Maxim Yu. Osipov" Cc: isar-users Subject: Re: Upgrading bitbake in isar Message-ID: <20181102105508.79c689a6@md1za8fc.ad001.siemens.net> In-Reply-To: References: 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: 3PKCYCOlQnDY Hi, i already did that a few months ago and just went for latest-greatest. And as expected that worked without much headache, after all it is only our build tool which seems to be mostly backward compatible. I remember a few warnings that would probably have required recipe updates to silence them, but it did build on the first try (even the whole thing in your CI). After that i spent some time on wic, which was not that easy. So i suggest "1.40". If you hit any blocking points a lower version might also be ok, but i would not expect any. The trickier thing would be to make Isar properly use the new bitbake after the bump. (using new features, removing workarounds and alike). Henning Am Thu, 1 Nov 2018 13:45:20 +0300 schrieb "Maxim Yu. Osipov" : > Hi everybody, > > I had several times requests regarding bitbake's upgrade in isar. > Do you have any suggestions about bitbake's revision to fast-forward? > > Kind regards, > Maxim. > > -------- Forwarded Message -------- > Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment > Date: Wed, 31 Oct 2018 07:39:01 +0100 > From: Jan Kiszka > To: Harald Seiler , isar-users@googlegroups.com > > On 30.10.18 17:44, Harald Seiler wrote: > > This patch allows adding DL_DIR to BB_ENV_EXTRAWHITE > > and then specifying a custom DL_DIR in the environment. > > > > This behavior mirrors the one in poky. > > > > Signed-off-by: Harald Seiler > > --- > > bitbake/conf/bitbake.conf | 2 +- > > We do not patch bitbake so far. Is this fix in upstream already? Then > let's fast-forward bitbake to that revision. If not, send it upstream > first. Local, isar-specific changes go to isar-bitbake.conf. > > Jan > > > meta/conf/isar-bitbake.conf | 2 +- > > 2 files changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/bitbake/conf/bitbake.conf b/bitbake/conf/bitbake.conf > > index a460df4..ba0d68b 100644 > > --- a/bitbake/conf/bitbake.conf > > +++ b/bitbake/conf/bitbake.conf > > @@ -23,7 +23,7 @@ CVSDIR = "${DL_DIR}/cvs" > > DEPENDS = "" > > DEPLOY_DIR = "${TMPDIR}/deploy" > > DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images" > > -DL_DIR = "${TMPDIR}/downloads" > > +DL_DIR ?= "${TMPDIR}/downloads" > > FILESPATH = > > "${FILE_DIRNAME}/${PF}:${FILE_DIRNAME}/${P}:${FILE_DIRNAME}/${PN}:${FILE_DIRNAME}/files:${FILE_DIRNAME}" > > FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', False))}" > > GITDIR = "${DL_DIR}/git" diff --git a/meta/conf/isar-bitbake.conf > > b/meta/conf/isar-bitbake.conf index 666c4a3..39e73f6 100644 > > --- a/meta/conf/isar-bitbake.conf > > +++ b/meta/conf/isar-bitbake.conf > > @@ -19,7 +19,7 @@ > > # OTHER DEALINGS IN THE SOFTWARE. > > > > WORKDIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PF}" > > -DL_DIR = "${TOPDIR}/downloads" > > +DL_DIR ?= "${TOPDIR}/downloads" > > SSTATE_DIR ?= "${TMPDIR}/sstate-cache" > > BUILDCHROOT_HOST_DIR = > > "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-host/rootfs" > > BUILDCHROOT_TARGET_DIR = > > "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-target/rootfs" > > -- 2.14.1 >