From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6823313354988191744 X-Received: by 2002:aa7:df85:: with SMTP id b5mr3595271edy.298.1588790976849; Wed, 06 May 2020 11:49:36 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:d1da:: with SMTP id bs26ls1554792ejb.10.gmail; Wed, 06 May 2020 11:49:36 -0700 (PDT) X-Google-Smtp-Source: APiQypIZWwBA9M+bT0wsKS8AGt5OAggR/n0N4nBo026ACWVsXRQEJHeoFELr0rSdwJ3YlxD8gglC X-Received: by 2002:a17:907:210d:: with SMTP id qn13mr8816661ejb.376.1588790976285; Wed, 06 May 2020 11:49:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588790976; cv=none; d=google.com; s=arc-20160816; b=XdKO8YskqV0jZS7rNh+zAC/iqQMq2Pdp2XxkxGeuY62f2qLHu7IqLrmxUE9ucS2VZb 1p0E+FO1iLLm1PogXJKMoi6zqr4ut3soJ7asYlF1kAuTpGCm10Lw7tcWwBXbmWaK3TF9 wrkY/9obPMjTlwzEtUGc3SBgNVCaqfRZCLZkY9MPe7Gpd3lwm+4FXH3SRlxWqyaGMvKY soN+YhkSdULomv8f1NHb422AtGJpT69B67a+favyfliHgk7p69cGj7U11r3EjoPpjyCg xIuLEYnGaAq2UkQfo3TcqYAYCdKJcc8cpkDhUvbEZC3PW/c2CSLaEMVBN9E2vOqVqUVg 5sbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=Q7rqNlBBJmhgALZfSIlsfW1/2kGV/WiXblIxCNSqHAI=; b=P5ZWW8yIUCzpZIsRImy1uQca9sPVI8XT5wArRg4/Y4p07Zx5i+UT4yRBpeECTbcp5P WU0eXUNgJMcUOOaPYhVFzYE4HWSk2ZtgoLGDOLrEnEQIx2xzz6ROEntSFvWKe6okeXTV UIDx3n53ubGXYCQ50+ccEbshT8+GzqOMupHFmxe/yhurTaKzfTKuA/CPkZVghcOx2QhZ biyK/4e6X/wryet8mejiJHEMmOZ5fM/7cJ6nTO1eiSmAj8VYan23zieQxaFwbsuQuvU4 K5QHzCbqCInQ/SAY6NCE4mij5efdcp1CfjcWwc0FPMFfI9mKsCrp8Uc7tPJ4pjncoRfo SRVA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id v18si150461eju.1.2020.05.06.11.49.36 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Wed, 06 May 2020 11:49:36 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (dslb-002-207-018-045.002.207.pools.vodafone-ip.de [2.207.18.45]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 046InXTg005360 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 6 May 2020 20:49:35 +0200 Date: Wed, 6 May 2020 20:49:28 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH 1/2] meta: remove dead code from buildchroot script Message-ID: <20200506184927.m454nzwzixri6w6v@yssyq.m.ilbers.de> Mail-Followup-To: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200506174044.1b4cf37f@md1za8fc.ad001.siemens.net> User-Agent: NeoMutt/20180716 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: VNvYUtRPjVzm On Wed, May 06, 2020 at 05:40:44PM +0200, Henning Schild wrote: > 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. Not to mean your patches are useless, those look good to me, I'd like to apply them in the course of the usual review process. My response was aimed at sharing the current state of the analysis to move forward faster and avoid duplicated effort. > 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. Seems I haven't described it clearly. The hen-and-egg problem I refer to is: Current state: Don't parse Build-Depends of e.g. libhello-dev to avoid maintaining own parser -> use mk-build-deps to generate a dummy package that Depends on Build-Depends of libhello-dev -> mk-build-deps in bullseye seems to generate a source package that has Build-Depends itself. What now? We have to install Build-Depends of libhello-cross-build-deps before we build and install it. So I don't think this is a Debian bug, it's a matter of how we handle installing Build-Depends of e.g. libhello-dev. Yes, we'll deal with that in a second step, this explanation says nothing against your patches. The solutions I was talking about: Option 1: If libhello source package is in isar-apt, the Debian way would be to apt-get build-dep libhello. If not, we should look at having it there. Option 2: If the above is not possible ATM, we should look at parsing the strings. Seems that dpkg has a Perl API. From ELBE folks I've heard that they use python-debian (not sure whether it has this specific feature). I agree that it should be an upstream solution. However, we might need to maintain it from time to time. > At the moment i will not be able to do that, i just felt i should fix > my code that swallowed the debug output. Got it, I see no problem with that. With kind regards, Baurzhan.