From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6823313354988191744 X-Received: by 2002:a19:2389:: with SMTP id j131mr5783649lfj.116.1588779810685; Wed, 06 May 2020 08:43:30 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:ac2:5a0e:: with SMTP id q14ls431199lfn.3.gmail; Wed, 06 May 2020 08:43:29 -0700 (PDT) X-Google-Smtp-Source: APiQypLJyGesXdr71fQYQ/NqmGGJORgqnzomYYMWDxA9J8goEX4+1P5HOxg6m0RZjw8v/g7WOP40 X-Received: by 2002:a05:6512:202:: with SMTP id a2mr5616268lfo.42.1588779809661; Wed, 06 May 2020 08:43:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588779809; cv=none; d=google.com; s=arc-20160816; b=p8Uw/1fA4VZHs2kYaDq7RvZpB1078BQG4QdGRPjecVY3X9SgOteAJGQGKLNzaCjVUr BfkbFo+hUTN5v2o1Y2iOg4gF4JkFv0U+9LJNVyrn8XHvejFBFYQ96Ab3RKG33hDFTc99 uuJHJLwOwU5HdaN6wOipSJoIgxpYm+BgCEjzXJQIF4ab2chClZqtn3Oxj/WBJPlv5yhq 8QIuA0zcc1f9rHazWC+AKI1EUwI+8z3RukGcbapkKdYcmeS3ciULAh3XsETNIYYAts/r j7wBjGIOfn7KEfoUhJhRAWCYtmSAj0BuuwP2yXx15nAlVH804Zgb2BIzJXJIUEe0bxiJ PtpA== 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:from:references:cc:to:subject; bh=CrxfqvP5rx5vxO8d+XZ9GrijLfNOVYQfvB6sDgupzIs=; b=E09BT5OW0BzVuX6Uggk1zzutwhRY/KBOZxjR+3Een+WswDi3CXkJLPWNyJa/ZH+E+3 IYjWvFAT4By3JyGs0pxRmdA3C1WI88MFHIFxKA4436VSpIgCPQAY2nwZQalCQxn/IiFY 9O7HqKA1YU+CjILGG39jxW++Ke6IOzKmh3W05G3ZEdWS1BkeVzwMyL8ke+qwANXrZUpc z2ulqtAWv/awEmnxeGHRLOC9flq8BTTvq8JLjHPvkx8Ue0bsdzFPVeR0R6WCIpTa03Lj 50gRvAjCofzUblYvC3pcRc7+w/v2Paae3PrWk87HxmW52l0rOFUkRv0xbmkSaX43jiD2 BSNQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@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 q24si179592ljg.4.2020.05.06.08.43.29 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 May 2020 08:43:29 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@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 046FhSVg008697 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 6 May 2020 17:43:29 +0200 Received: from [167.87.32.230] ([167.87.32.230]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 046FhRSh007730; Wed, 6 May 2020 17:43:28 +0200 Subject: Re: [PATCH 1/2] meta: remove dead code from buildchroot script To: "[ext] Henning Schild" , Baurzhan Ismagulov Cc: isar-users@googlegroups.com References: <20200505110026.6390-1-henning.schild@siemens.com> <20200505130234.0af1fc06@md1za8fc.ad001.siemens.net> <20200506085711.hvzfrhkeyfawnepc@yssyq.m.ilbers.de> <20200506174044.1b4cf37f@md1za8fc.ad001.siemens.net> From: Jan Kiszka Message-ID: <40c74594-1bef-6ea0-28a9-9c3cdb9c4d50@siemens.com> Date: Wed, 6 May 2020 17:43:27 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200506174044.1b4cf37f@md1za8fc.ad001.siemens.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: 2DjqIT5MAA6y On 06.05.20 17:40, [ext] Henning Schild wrote: > 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. Yes, the issue with bullseye is no single patch regresion, it also effects today's next. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux