From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6823313354988191744 X-Received: by 2002:ac2:4a72:: with SMTP id q18mr5574071lfp.115.1588779657561; Wed, 06 May 2020 08:40:57 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:8155:: with SMTP id t21ls636852ljg.5.gmail; Wed, 06 May 2020 08:40:56 -0700 (PDT) X-Google-Smtp-Source: APiQypI/GC/n0O+NhwQu4iF8m9hd3wT4KH/iWIfNR98z3HzMSzrInRvY7yRbcEwqk5iepFpZKL+q X-Received: by 2002:a2e:3813:: with SMTP id f19mr5324735lja.216.1588779656210; Wed, 06 May 2020 08:40:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588779656; cv=none; d=google.com; s=arc-20160816; b=LE7WNXllZG/72ord6KrsOTo0l9cq87DC26b4MBx2YVKCm0Iqg06kjvo+pg+cB7LAC6 MFMcbROtYqAlI6fxZYjks1GEXmovu/KMvQc6fVudNMUDkQ7mFrvOSo7zDgcynXkvAHKW sY4XwIyWQgi1k+Ui1sT2cG6jRQ6YRif6c4R/61UZOBDYXHMEESQV6mKNDLUtFYxu3WMs gsACdWYm9Ee4QDPi8Rx3J6b3zBgPpuPpSwRORnHT4aD8FYFQFdqlojl/26h8q4cQCr9x EmE6q83kZrbmblY/txedarJElJaTLjoTeRhPALWaFMtonfEGHGMkwrhfg9VRce2nI5mF VR0g== 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=Eze2MhGE3cXX/hpyH//yxKKFOACPgcY0iMFQtkKsqkg=; b=Y5QgBcqqvpLtRW/MAZvrYmlgFSjeC9kJaCW3qlel+PzYhiB5z3++Ywn/2vMa6xAtoI QqDFJWBKYVKhFafsWE54e79WdvKs2vhShNgHMPdYQLlcm20MsDn2Qeoc8u4hgw9OKbYg GDc6F9MGIm89bx3ojIVHBLlXIJfx3bIlUTmqBCbGRU8LoFjtUMx+ZylXkLnHRqpFU9PT FBdqod2qCpOPm0O/NchlTHESCUHKuEbH0bFa7i5+2noG9NkdKXKtCkfa+tC+hPLrHpet qK08hbYXAl+TpGz1Rde0aMjy1DC7g3J68G/we1xtPgYLzvobJLuxRnNGBjgn5zC42kbc pVPA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id q24si179139ljg.4.2020.05.06.08.40.56 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 May 2020 08:40:56 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id 046Fetar005851 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 6 May 2020 17:40:55 +0200 Received: from md1za8fc.ad001.siemens.net ([167.87.7.153]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 046FesTU004127; Wed, 6 May 2020 17:40:55 +0200 Date: Wed, 6 May 2020 17:40:44 +0200 From: Henning Schild To: Baurzhan Ismagulov Cc: isar-users@googlegroups.com Subject: Re: [PATCH 1/2] meta: remove dead code from buildchroot script Message-ID: <20200506174044.1b4cf37f@md1za8fc.ad001.siemens.net> In-Reply-To: <20200506085711.hvzfrhkeyfawnepc@yssyq.m.ilbers.de> References: <20200505110026.6390-1-henning.schild@siemens.com> <20200505130234.0af1fc06@md1za8fc.ad001.siemens.net> <20200506085711.hvzfrhkeyfawnepc@yssyq.m.ilbers.de> X-Mailer: Claws Mail 3.17.5 (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: qg6R39kj6xVW Am Wed, 6 May 2020 10:57:11 +0200 schrieb Baurzhan Ismagulov : > Hello Henning, > > On Tue, May 05, 2020 at 01:02:34PM +0200, Henning Schild wrote: > > The first one is a cleanup. And the second one can hopefully help > > find out why bullseye currently does not build anymore. > > Thanks. FWIW, at least some of the output leading to the problem can > be seen here: > > http://ci.isar-build.org:8080/job/isar_vs_devel_3_fast/9/consoleFull > > The relevant part is: > > | + mk-build-deps --host-arch armhf -t 'apt-get -o > Debug::pkgProblemResolver=yes --no-install-recommends -y > --allow-downgrades ' -i -r debian/control | dpkg-buildpackage: info: > source package isar-exclude-docs-cross-build-deps | > dpkg-buildpackage: info: source version 0.1 | dpkg-buildpackage: > info: source distribution unstable | dpkg-buildpackage: info: source > changed by root | dpkg-architecture: > warning: specified GNU system type arm-linux-gnueabihf does not match > CC system type x86_64-linux-gnu, try setting a correct CC environment > variable | dpkg-source --before-build . | dpkg-buildpackage: info: > host architecture armhf | dpkg-checkbuilddeps: error: Unmet build > dependencies: build-essential:native | dpkg-buildpackage: warning: > build dependencies/conflicts unsatisfied; aborting | > dpkg-buildpackage: warning: (Use -d flag to override.) | Error in the > build process: exit status 3 | dpkg: error: cannot access archive > 'isar-exclude-docs-cross-build-deps_0.1_armhf.deb': No such file or > directory | mk-build-deps: dpkg --unpack failed | WARNING: exit code > 2 from a shell command. | NOTE: recipe isar-exclude-docs-0.1-r0: task > do_install_builddeps: Failed > > A possible scenario is that the temporary package created by > mk-build-deps now implicitly or explicitly Build-Depends on > build-essential:native, which isn't installed at the time of > dpkg-buildpackage. If we can verify this, we could install the > missing Build-Depends before mk-build-deps. > > Which would be a hen-and-egg problem, since mk-build-deps has been > introduced to avoid manual parsing of debian/control fields. The > ultimate solution could be to add all packages to isar-apt and > apt-get build-deps e.g. libhello-dev. I don't know whether that could > be done today. Meanwhile, I still think that parsing the fields is a > viable option (with the goal to have the solution upstream). I would conclude that those patches seem to work. We can merge them later with the fix, but whoever comes up with the fix might want to use them. I think if we find a hen-and-egg problem we found a Debian bug and can lean back after reporting. But that needs further analysis and someone taking care of the issue and possible involving upstream. At the moment i will not be able to do that, i just felt i should fix my code that swallowed the debug output. Henning > With kind regards, > Baurzhan. >