From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6519112020741062656 X-Received: by 10.28.57.139 with SMTP id g133mr134312wma.28.1517909889616; Tue, 06 Feb 2018 01:38:09 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.231.15 with SMTP id e15ls1993114wmh.8.gmail; Tue, 06 Feb 2018 01:38:09 -0800 (PST) X-Google-Smtp-Source: AH8x227+xkWUTse94Ig5qK9i7lknRBWPuQ73Crh6oX6yGVm0g9Xxkm8tyMB25A3OyWAapIJlmLV8 X-Received: by 10.28.3.11 with SMTP id 11mr162245wmd.4.1517909889061; Tue, 06 Feb 2018 01:38:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517909889; cv=none; d=google.com; s=arc-20160816; b=zuAlS+E850g/+RI1mcN68O5GYnwuuUs1RhmPvAWlyHsnXdMVJcerxnZ52+icB2UEtJ MWpBSwUmSbv2TzQCGapoW+6CtJXoc+tHX5OqB7/ZISvQvkBz40LiYbd2USzLp0FfSSfl EU2qyD+kSMnr3W8p5/ng7d+DisWZXBLUYwPM1vwRZQZk3G9gk9bkrQCTUSD/ovZQUjWs 1bknH3c9hkPZV4q1WZmQbYtpAXI/I2hC9/oAkpJjdtuFqtYBkGv8vUtNJ2O0KRrtDSWQ mXN0pSFCyNQu3470PAX0SiALkqANPfcUezasa5UWAtxdBFCLAaNcHFtcXc76InJGSxD7 OFIQ== 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:references:to:from:subject :arc-authentication-results; bh=yA89KNDppXnF/UGCvgbmkXZMGnBnfgRelgbQvg8g0xA=; b=K1Z2ksP0thw5wihsnleI8kT4gi7hdody474sYT1qcqFRCCHVk4WkKzdBB6ijS7aQ5l ya73YIb10LYITTf7yCNgaSd27/2VdO1O6xCQcCdifYVco8Htb/2WfHkxbqVq1uARn7Lq XjgY06mr0Y7ChiZj+YRKq/uHDVQBCGxm+alCGSsPADeOyzBvvEkbvT8mU57AOK//6Tpq kOTPzfeMGbwsZuUoYNBZLUiGSMYgsxJCLvO7DjP5dxeT6GPjK6WhyOIzL3Dw9L/5dZ3Y qnyWLqF+jELZwJPlUTcbp65jqoyS+cx4YPFOXhs5VsmIbS3E39auN8wcJ9F/7Ur6rx5a MFLQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id v8si695058wrg.2.2018.02.06.01.38.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Feb 2018 01:38:09 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w169c8Il024295 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 6 Feb 2018 10:38:08 +0100 Received: from [167.87.10.11] ([167.87.10.11]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w169c8mK025528; Tue, 6 Feb 2018 10:38:08 +0100 Subject: Re: [PATCH 2/2] buildchroot: Permanently mount '/dev', '/sys' and '/proc' From: Jan Kiszka To: Alexander Smirnov , isar-users@googlegroups.com References: <20180205164347.28375-1-asmirnov@ilbers.de> <20180205164347.28375-3-asmirnov@ilbers.de> <604637ca-63f4-524a-0484-34f38f706919@siemens.com> Message-ID: <4364b432-f199-d2f7-3d26-32b0cfc91c0b@siemens.com> Date: Tue, 6 Feb 2018 10:38:07 +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: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: TM/WIt9F0fzX On 2018-02-05 19:06, Jan Kiszka wrote: >>> And when I restart the build that I interrupt after buildchroot was long >>> finished, that task is still rebuild - and that fails, maybe because of >>> preexisting artifacts. >> >> That's the known problem, we have no do_clean task implemented. Re-run >> on existing tree is not officially supported for now. > > That should be fixed, or our turn-around times for Isar development will > explode! This is really an urgent must-fix. I'm doing full rebuilds over and over again now, just to test small changes down the pipeline. Do you already have an idea how to prevent the buildchroot rebuild? I suppose it's caused by the new prepare task, right? Can we achieve that without invalidating the buildchroot setup? Jan