Re: sbuild migration problem: how to jump into SBUILD_CHROOT with build dependencies installed

[Florian Bezdeka <florian.bezdeka@siemens.com>]

Hi Anton,

On 19.08.22 10:30, Anton Mikanovich wrote:
> 19.08.2022 11:25, Florian Bezdeka wrote:
>> Hi all,
>>
>> I'm trying to update Isar to the latest next version in one of our
>> downstream layers. This is the first version for this layer that uses
>> sbuild.
>>
>> One of the recipes has the following dpkg_runbuild_prepend() defined:
>>
>> dpkg_runbuild_prepend() {
>>      sudo chroot --userspec=$( id -u ):$( id -g ) ${BUILDCHROOT_DIR} \
>>          sh -c "autoreconf -fi"
>> }
>>
>> In the pre-sbuild times this task was executed *after* the build
>> dependencies have been installed but *before* the dpkg_runbild task.
>>
>> With sbuild:
>> - There is no "install build dependencies" task anymore
>>    Installation of build dependencies is done by sbuild internally
>> - The task is now executed *before* build dependencies are installed
>> - I still could chroot into ${SBUILD_CHROOT}, but the build dependencies
>>    will not be there
>>
>> Is there any possibility to jump into the ${SBUILD_CHROOT} after build
>> dependencies are installed but before the actual packet build?
>>
>> Best regards,
>> Florian
>>
> Hello Florian,
> 
> Correct way to implement this is to move autoreconf into debian/rules.
> 

In this simple example for sure. But: There might be recipes where
debian/rules is not directly "accessable", forcing me to wait for 3rd
parties to update their build process (or patch things in my layer) and
all of this just because I tried to update Isar...

If there is no way to jump into ${SBUILD_CHROOT} with build dependencies
installed we have a (very minor) regression.