From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6491554293275951104 X-Received: by 10.46.19.1 with SMTP id 1mr14011ljt.15.1512994600230; Mon, 11 Dec 2017 04:16:40 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.80.14 with SMTP id e14ls964737ljb.17.gmail; Mon, 11 Dec 2017 04:16:39 -0800 (PST) X-Google-Smtp-Source: ACJfBot4ZpYNHlM1zE6xcHYvsrGpVzsaCigz3VaAhxRb8mOdE817otusMxUp5QXpl8EwIkvM66G2 X-Received: by 10.46.85.202 with SMTP id g71mr13476lje.19.1512994599761; Mon, 11 Dec 2017 04:16:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1512994599; cv=none; d=google.com; s=arc-20160816; b=NsZXNnCAiqiaXqcx+0THOni21cCkpcHqg4Vp9rDFPJJh3VWfQ9yUyzXf3jl230g1/R wUHGvnGPOWnyABax/+IR194Fu+xhshzniTgwUSHZG2b6fGcO22C6NzYQ5qbw5lKio0gl n/EHnsktdrVcB8YamriRIrwaeGT7HyQs4mH74uH3mubosrLUUG6xE/U1Q6gRSm3Aww7b J9kpwTYGfoRk8hQYZRGlu/rWBfZMHlJxWPle8w9re9Qq5B+DHKeynUF+Gx/CKCwvOv2u OgviP1kr1w/Vg487hnyQrjWW6GeNXrLQYr9E1gt27AH8T/I+tMmyKt+ef/1fp5ez9jfF cInA== 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:arc-authentication-results; bh=FWcOm48ByEKqVPYNOvxAsvMq8MGkeE270FtLzEclKs8=; b=J5v8fc71TB3pbSej0D8j+baNGhE40rtq0yxEs6LFrlAiYTtSiPTXHtFbZGlGzCZA8d BLONoRQOFg5ydUQNTodQu/rh8Dy0ut0GB2RNICd1VeOKZiMvJzZJCsHbTa7Lz/d4NRfF 4E5qGPo8z40IH1a0xoTx35I68QJ8ZKMBw1IZU5pJxcCbYYwI/evdR/LUMqTbEXaMNI1C 8u0vzJJH2QEs2LEYqRf7kHuoErbcmqZGQ90i/0s99+REB7CPxHx0Lmn+HaaNz+g+mi5E m23J/FChYwhjV4E5k1t22++lVaOFg89gUF0B/xCg1pSPziJw0AKsPmodrGIubeF9UmFw eq8Q== 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 g77si1364544lfl.5.2017.12.11.04.16.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Dec 2017 04:16:39 -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.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id vBBCGZqO002892 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 11 Dec 2017 13:16:35 +0100 Received: from md1em3qc (md1pvb1c.ad001.siemens.net [139.25.68.40] (may be forged)) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id vBBCGZhU023457; Mon, 11 Dec 2017 13:16:35 +0100 Date: Mon, 11 Dec 2017 13:16:34 +0100 From: Henning Schild To: Alexander Smirnov Cc: , "Storm, Christian (CT RDA ITP SES-DE)" Subject: Re: [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks Message-ID: <20171211131634.066ad96a@md1em3qc> In-Reply-To: References: <20171208075806.dxvaf7harsupg7co@MD1KR9XC.ww002.siemens.net> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: ZZUMtQqbOaTm Am Mon, 11 Dec 2017 12:23:40 +0300 schrieb Alexander Smirnov : > Hi Christian, > > On 12/08/2017 10:58 AM, Christian Storm wrote: > > > >> 2. 'do_cleanup': This task is executed after all the packages are > >> deployed. Some notes: > >> - This task also should not have stamp. > >> - This task depends from the recipes listed in IMAGE_INSTALL. > > > > This breaks build dependencies when building two packages from > > source (same example I've given in other posts as well): > > > > Consider A-dev required by B, both to be built from source. B cannot > > install the A-dev.deb since B depending on A-dev's deploy_deb() and > > installing it the ugly way via dpkg -i (as no other option is > > currently available in Isar) puts B as late in the task order so > > that it's git repo is not mounted anymore. Failure. > > > > If A-dev installs it's produced .deb as last step in its > > dpkg_runbuild(), which is also ugly, then there's a potential race > > in dpkg. Failure. > > Seems I don't fully understand your usecase, could you please comment > if it's correct: > > 1. You have two Isar recipes A and B that build packages from source > code. > > 2. After building of package A, apart from binary A, A-dev also > provided. > > 3. Package B depends on A-dev. > > Also, have you added dependency from A in B recipe? Dependencies will not help here, Isar simply does not support that case ... yet. You have B depending on A both at runtime and on build-time. So you need a buildchroot to build A in. And for B you need a buildchroot which has A installed. To get the buildchroot for B you either have to install A into its own buildchroot or multistrap again. I think Christian currently installs A, but with "dpkg -i". I think multistrapping again would be overkill. IMHO the best solution would be to install such packages in buildchroot with apt-get, after they have been repreproed to the "Isar" repo. I suggested improvements on "[PATCH 0/4 v5] Isar apt deployment" but the feedback was delayed until a v2. Essentially deploy_deb needs to reprepro, do_populate needs to go away, builchroot needs aptsources=Isar in its multistrap.conf. Now the apt-get in build.sh should work. Henning