From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7062656987288305664 X-Received: by 2002:a2e:8789:: with SMTP id n9mr661322lji.277.1644576847995; Fri, 11 Feb 2022 02:54:07 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:22d1:: with SMTP id g17ls5155786lfu.2.gmail; Fri, 11 Feb 2022 02:54:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJzdTWJeF2GTvhEYKf4vU3YmZG4whsMgQrCuNtIelWcQl6VvVRU2ax/E8ITYxV3LB/GWE4qV X-Received: by 2002:a05:6512:308b:: with SMTP id z11mr837135lfd.512.1644576846789; Fri, 11 Feb 2022 02:54:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644576846; cv=none; d=google.com; s=arc-20160816; b=VwURFCoJX1nA7a0klmj2YZsHpCJlUO76Y3pKSEeWZlna9ZLcrcpCcWsfvsygREILBT Wzz1wXMm2MXXOpf5u5cFSg0IWAEEIHA2Yjg5fmtOLw01VgHFMci3p+DQ3qy2RrE373US RZC6myj3etry2dWE8MYdooOM660VTAOzlO9avSj3xzw8JnSgt/h8CMNiSbZethMElsvR gJ670QN6JRm66HQbN34XfF3CU158dHutmjnL7ULj3t2FjBRlRSpqJZ4AJs3uawMBuHkK W95EXvj6dS3SUGYloh8iCRY2ub+jaIE5ilKo01h64YUOEF6oiUSUWUFn49G712m2vR7w vo6w== 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:to:from; bh=lHwZXoZyKe4bBCHM1xHVgzbzCjbVTbcOBLKJng7nsz4=; b=WsifcIbPpb7Y8WGwImdwujNNigzlRc+6daMir+pFbPSO7rRxSCbnnY0QARbCrgyNDj EQeJfCdfoGiWTXUZR2pgb5TzY1MM7HBwkp105EL9QttzMuoaq3gW46cTPfHu1m7RFLZH BtQHr0P7Khxwifon3ivW2RQSYbwjSClMnpSCmChjVp+ZHZtHLLkx5a/QkReQApF+fAsP E5wFCDy5XpHl+LyTIzaO9cFNOJRNZY55gEvbHZFPkglj0WBGqiMiez3VJGS6PFLZH11d 1XpzHIvFpsibMpQdAuJ2aCuwGreB0T0GQy+CLY+VntGT4WhE64JSImhudfq6+sdUHLsk JHMw== 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 z2si866078ljh.2.2022.02.11.02.54.06 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 11 Feb 2022 02:54:06 -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 21BAs5tk002198 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 11 Feb 2022 11:54:05 +0100 From: Uladzimir Bely To: isar-users@googlegroups.com, quirin.gylstorff@siemens.com Subject: Re: Question related to Sbuild CLEAN_SOURCE Date: Fri, 11 Feb 2022 13:54:03 +0300 Message-ID: <3349320.sQuhbGJ8Bu@home> In-Reply-To: <29092d94-9261-07d6-7ebf-240dbbb435c4@siemens.com> References: <1b5ef299-ec8d-c180-c2b6-505294f5484b@siemens.com> <2591024.vuYhMxLoTh@home> <29092d94-9261-07d6-7ebf-240dbbb435c4@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: Q5HysYm9W4L9 In the email from Thursday, 10 February 2022 12:10:47 +03 user quirin.gylstorff@siemens.com wrote: > On 2/10/22 09:47, Uladzimir Bely wrote: > > 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? > > Ah sorry, > > you need to add the SWUpdate option to the build. The kas command would be: > > ``` > /kas-container --isar build > kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/ebg-swu.yml > ``` > > or you build SWUpdate from the devshell. > > Kind regards > Quirin I tried this - and yes, I also faced this problem with "dh_clean --with lua". There are 2 ways to deal with it: 1. We can simply add "--no-clean-source" to sbuild parameters. In this case sbuild itself doesn't trigger additional "dh_clean" before build. 2. We can switch to building from .dsc file instead of building from unpacked source directory (e.g., firstly create .dsc file by dpkg-source, sencodly, run sbuild passing .dsc as argument). In this case sbuild also doesn't call dh_clean. Both methods work, but the second looks more debian-friendly. BTW, I faced some other build issues with "isar-cip-core": 1. "efibootguard" recipe attempts to deploy "efibootguardx64.efi" and "bg_setenv" binaries directly from source tree. This doesn't work with sbuild, especially in case of building from .dsc file. Moreover, "efibootguardx64.efi" binary doesn't even belong to any output .deb files. I consider this binary should be added to .deb file and deploying should be done from it (e.g. using "dpkg --fsys-tarfile" for extraction). I can submit a patch if needed. 2. "swupdate" is built from git branch "debian/master". I had to add "-git- ignore-branch" to GBP_EXTRA_OPTIONS, to skip the error, like "not master branch used". 3. Finally, I still have build error with "swupdate": "The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: sphinx but it is not installable" -- Uladzimir Bely