Re: Question related to Sbuild CLEAN_SOURCE

[Jan Kiszka <jan.kiszka@siemens.com>]

On 09.02.22 16:14, 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.
> 

Resolving that concrete issue is one thing, but using sbuild in its
"convenience feature" mode for Isar is another and not that easily fixable.

> 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
>>
>>>> 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.

What will that mean for layers? Patching Debian packages "ad-hoc" is not
an uncommon use case anymore. In fact, bringing Debianization in via
Isar/bitbake is even more common and would be equally affected.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux