From: Anton Mikanovich <amikan@ilbers.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: sbuild migration problem: how to jump into SBUILD_CHROOT with build dependencies installed
Date: Fri, 19 Aug 2022 11:30:41 +0300 [thread overview]
Message-ID: <4dd276e8-a0db-4215-6d2a-eb74282d0c94@ilbers.de> (raw)
In-Reply-To: <5ac8a864-5a1b-6f03-2318-68c6b8d612f0@siemens.com>
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.
next prev parent reply other threads:[~2022-08-19 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 8:25 Florian Bezdeka
2022-08-19 8:30 ` Anton Mikanovich [this message]
2022-08-19 8:36 ` Florian Bezdeka
2022-08-19 10:32 ` Baurzhan Ismagulov
2022-08-19 13:05 ` Florian Bezdeka
2022-08-27 8:44 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dd276e8-a0db-4215-6d2a-eb74282d0c94@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox