From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6649357282775662592 X-Received: by 2002:adf:ee51:: with SMTP id w17mr246085wro.17.1548257345685; Wed, 23 Jan 2019 07:29:05 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:94a6:: with SMTP id 35ls680938wrr.15.gmail; Wed, 23 Jan 2019 07:29:05 -0800 (PST) X-Google-Smtp-Source: ALg8bN5sHapgNiAa9rwk7FMqbJ/0VGiOBOthJ+i3vyzw0IlsbDCZ5eopQI2G7NJ0Ms+5d4LuPtrd X-Received: by 2002:a5d:6b52:: with SMTP id x18mr259354wrw.19.1548257345295; Wed, 23 Jan 2019 07:29:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548257345; cv=none; d=google.com; s=arc-20160816; b=uPwFm9krJmb2dDfJsUaRmxHJNK9/pG4/C8e1Z/xnE8WY9TsN0bIAHjKWZ/WJoKirU4 znbnFcsA2BEwjrCdqiU1l853p9b8/uNVJlyKQJTxSVwjblH+uIXwuxnblG1sA/zZ7354 SaMsMaz+/5lZnWhrZsGpjd2u1j3DXcQR8HJNn9SaUM90fQt+sQkJcJxPpb+6DP/+wanX JilB7vseFuGf0vmAKCrpZrjNioefS426m0qWdmu3BC3FbB3lFX8vqbYrLGRa13TIfAnQ KGF+2r/g9Y310w/ThkESepRppb2L21Za++ggFZelRhGeHhbjSRSDf6SVuxbwhvjLjmo2 NL6g== 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=lb8h5E0/NjI0hQ/2CtJYmu/5QtCEwdEZVAPfKQoP27E=; b=YnbNvyQYq5a3kEWe/PC9bqTdzhDfNN7QSxV5nAm6i3rXzR/DlyWiCQDBW0ycEoKxL6 Sx4WZ4/iVx3kvUDxPBiqlj0uGc+YMe5X1F1nVpgyni9hruQh3rBtIj9wzsFZWdU/4HzG inAUdC885AKL6PlEzBUxVuYeAtuMbkKFezWN2WiJ0Xdz9LHROg2RtGjmxTmR2hS6TFkK L7vR4vVGUSZL912u/foEgilFBGl9Pi5Z81Pi+NNrjre3XbyXwUACmEE5eDVFtbfbG01o +j90l3NTVBwIfWnfR3QtsA3y8XIXdxHRG6u5tezlaCbvbN03Nw9zVu/Bf+n7OWFBm3om VqDw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id k39si3348532wre.2.2019.01.23.07.29.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 07:29:05 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x0NFT4qo016074 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 23 Jan 2019 16:29:04 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.0.45]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x0NFT4MM006000; Wed, 23 Jan 2019 16:29:04 +0100 Date: Wed, 23 Jan 2019 16:29:04 +0100 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: [PATCH] buildchroot: Perform upgrade after build dependency installation Message-ID: <20190123162904.12c9ba1b@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20190122180830.3aa8bef1@md1za8fc.ad001.siemens.net> 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: yK827SsIJJS/ Am Tue, 22 Jan 2019 19:19:58 +0100 schrieb Jan Kiszka : > On 22.01.19 18:08, Henning Schild wrote: > > Am Tue, 22 Jan 2019 17:22:14 +0100 > > schrieb Jan Kiszka : > > > >> From: Jan Kiszka > >> > >> When we partially rebuild after updating the version of a build > >> dependency of another package, we do not properly upgrade that > >> dependency in buildchroot. The reason is that "apt-get install" > >> performs upgrades only for the explicitly listed packages. But we > >> install build dependencies indirectly, we a meta package's > >> dependency. > >> > >> Resolve that be running an explicit "apt-get upgrade" after the > >> build dependency installation. This will ensure pulling the latest > >> versions for isar-apt. > > > > I am not sure i fully understand the problem given your description, > > but i get the idea. > > > > The mk-build-deps calls an apt-get that will not do anything even if > > builddep-0.1 has to be updated to builddep-0.2? Maybe you can > > address > > If you refer with "builddep" to the meta package that mk-build-dep is > generating > - no, it's one of the indirect dependencies it refers to. Concrete > case: kernel update, and kernel-headers will not be upgraded, thus > the module built against the wrong kernel. No i am talking about the package at the lower end. We have A -> B -> C0 + C1 + C2. A is the one we want to build, B is the artificial package, and Cxx are the ones on the "lower end". > > the problem with the "-t" argument of mk-build-dep? > > I've tried various switched to apt-get install, but it just reported > to not do the identified upgrades. I would prefer a magic switch as > well, so I'm all ears which one we may miss. Did the debian version string change to something greater? If not it should probably increase. Another option would be to "apt-get remove" a packages from all buildchroots on its clean, unless it was explicitly installed. But i guess what you came up with is fine as well, and less complicated. Henning > Jan