From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7062656987288305664 X-Received: by 2002:ac2:4c4b:: with SMTP id o11mr4599960lfk.253.1644482861269; Thu, 10 Feb 2022 00:47:41 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:ac2:4e11:: with SMTP id e17ls2596939lfr.1.gmail; Thu, 10 Feb 2022 00:47:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJwE1wSm+oIUpppOpgQFXY3RyU7ZHCYXvnbWwXto0bNNVR9tABFEaFcqAPLSV5Shg43I//oL X-Received: by 2002:a05:6512:1044:: with SMTP id c4mr4469214lfb.43.1644482860188; Thu, 10 Feb 2022 00:47:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644482860; cv=none; d=google.com; s=arc-20160816; b=0Fl6nOZwzqsNcOZMB0f4pSqSbK7B8O6lvVhJkmhFmE646r7sDpfxGKflH2ZOfp7E+8 KoUo0CEu0q3stPsf6071tE6Yz1uJcnQhrRYa+84Hmvr/hdM9K1ZAXlsyBDmNVqryAkLk G6KBJmJZgY2mc+M1OBc4qo9HGl95XApoblNyARlXH0N6jcFciyFI+aDtKGjbKFOZXU37 ktRxU+/DlI4yXBuwP4DwsWYZM5nslER+6co+L7Qnl1p842nt4NkeLSDB19rDD3CtrH6B EPOVMzDK82O1yhLo9y/vkxsI3PppI3LhQwvdNBH/N7Sd5rc0zCtiq4H8Kz22gQXQyv1T zsKA== 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:date:subject:cc:to:from; bh=UxvYR1jZ5pPh/3Xk8s1C1nk5xmPNUjhudMEwyLyH2aE=; b=ekyMyg1hIHcZJ1T/e/l9i5gh5j47sbJdtseh+KtzMtfDx1b7CAXjvvgQwOuM7RwEpG Z/0OtkCUQzU93KyMmFiDTMc3tpMfKHqjFFvxUwayF9VcELq4VGMSFUziwZH1mrLbgYwP /UoU7U6k2X7QAKIlvVkWfgRFScuDyTLcjjyugq+AMLokeRY108iaF1TztDp3DkPs3Hc0 cxpkws/rkedEfPhM8ivDpp1NfJxS8w/PVht6piW3f0WPoLr+M2mPwrtshgCKSw5js7fz ZaQfbXJIsAy0VTmuh0YKomq4o1dNmKKfJItipxsVnPghz1audfJHmmlrZFJ3lrg+t+r8 fehg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id z2si688729ljh.2.2022.02.10.00.47.40 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 10 Feb 2022 00:47:40 -0800 (PST) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from home.localnet (44-208-124-178-static.mgts.by [178.124.208.44] (may be forged)) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 21A8lcmP028935 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 Feb 2022 09:47:39 +0100 From: Uladzimir Bely To: isar-users@googlegroups.com Cc: quirin.gylstorff@siemens.com Subject: Re: Question related to Sbuild CLEAN_SOURCE Date: Thu, 10 Feb 2022 11:47:36 +0300 Message-ID: <2591024.vuYhMxLoTh@home> In-Reply-To: References: <1b5ef299-ec8d-c180-c2b6-505294f5484b@siemens.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: X97eB9CjUtWH In the email from Wednesday, 9 February 2022 18:14:22 +03 user quirin.gylstorff@siemens.com wrote: > On 2/9/22 12:52, Baurzhan Ismagulov wrote: > > On Wed, Feb 09, 2022 at 11:36:09AM +0100, quirin.gylstorff@siemens.com wrote: > >>>> - Is there are reason sbuild executes clean outside of the chroot? > > > > It would be interesting to hear what kind of issues you had due to that. > > If we rebuild a debian package with dpkg-gbp which uses for example > `dh-lua` (swupdate) the build will fail due to the missing installation > of dh-lua in the host environment. The solution to this is to install > dh-* in the build environment. > > ``` > gbp:info: Performing the build > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying use-gcc-compiler.diff > dh clean --with lua > dh: error: unable to load addon lua: Can't locate > Debian/Debhelper/Sequence/lua.pm in @INC (you may need to install the > Debian::Debhelper::Sequence::lua module) (@INC contains: /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 > /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 > /usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 13) line 1. > BEGIN failed--compilation aborted at (eval 13) line 1. > ``` > > You can fix it with documentation but it needs to be addressed. > > A project where this can be tested is isar-cip-core with the current > preintegrated sbuild[1]. > [1]: https://gitlab.com/Quirin.Gy/isar-cip-core/-/tree/test/sbuild Hello. I've tried this repository (master branch) on my side. It currently builds OK with Isar revision 33b5aa65 (default mentioned kas- cip.yml), it works with current isar/next as well. Also, I successfully built it wth latest isar/ubely/sbuild revision. Maybe there are some more specific steps to reproduce the issue you are talking about that I could try to check on my side? > > >>> But the actual input to sbuild is the source package > >>> (the dsc). Don't use sbuild to create a source package. The source > >>> package is the input to sbuild. The output of sbuild are binary > >>> packages, not source packages. > > > > It's interesting that he is mentioning it; we are currently performing > > this > > exact split for meta-iot2050. > > > > > > With kind regards, > > Baurzhan. > > Kind regards, > Quirin -- Uladzimir Bely