From: quirin.gylstorff@siemens.com
To: Johannes Schauer Marin Rodrigues <josch@debian.org>,
debian-user@lists.debian.org, sbuild@packages.debian.org,
isar-users <isar-users@googlegroups.com>
Cc: "Kiszka, Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>,
tobias.schmidl@siemens.com
Subject: Re: Question related to Sbuild CLEAN_SOURCE
Date: Wed, 9 Feb 2022 11:36:09 +0100 [thread overview]
Message-ID: <818250b5-fed8-8ff9-febb-6cbf61e0680f@siemens.com> (raw)
In-Reply-To: <164435326066.1656.13805705968480410488@localhost>
Hi,
thanks for the fast answer - I will forward the mail to the
ISAR mailing list.
On 2/8/22 21:47, Johannes Schauer Marin Rodrigues wrote:
> Hi,
>
> please keep me in CC as I'm not subscribed to debian-user@l.d.o.
>
> Quoting quirin.gylstorff@siemens.com (2022-02-08 15:40:40)
>> we are currently testing the integration of sbuild in ISAR[1] and have a
>> question related to the CLEAN_SOURCE behavior.
>>
>>
>> "When running sbuild from within an unpacked source tree, run the
>> 'clean' target before generating the source package. This might require
>> some of the build dependencies necessary for running the 'clean' target
>> to be installed on the host machine. Only disable if you start from a
>> clean checkout and you know what you are doing."[2]
>>
>>
>> As noted in [2] we observe that we need dh-<helper name> in the host
>> environment to execute the dh clean -with <helper name>.
>>
>> Our questions are:
>>
>> - Is there are reason sbuild executes clean outside of the chroot?
>
> Yes because if you don't know what you are doing (as it says in the manpage you
> cite) and you run sbuild from within an unpacked dirty source tree without
> running the clean target, then you might be building something that is not the
> source package you expect to be built.
>
>> - How does the buildd infrastructure deal with this behavior?
>
> The buildd infrastructure doesn't run sbuild from within an unpacked source
> tree so it will not run the clean target outside the chroot and thus doesn't
> need to have the necessary dependencies for running the clean target installed.
>
> The fact that sbuild is able to run from inside an unpacked source tree is a
> convenience feature which allows you to run sbuild without having to first
> create the source package. 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.
>
> Thanks!
>
Best regards,
Quirin
next parent reply other threads:[~2022-02-09 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b5ef299-ec8d-c180-c2b6-505294f5484b@siemens.com>
[not found] ` <164435326066.1656.13805705968480410488@localhost>
2022-02-09 10:36 ` quirin.gylstorff [this message]
2022-02-09 11:52 ` Baurzhan Ismagulov
2022-02-09 15:14 ` quirin.gylstorff
2022-02-09 15:37 ` Jan Kiszka
2022-02-10 9:59 ` Baurzhan Ismagulov
2022-02-10 11:27 ` Jan Kiszka
2022-02-10 12:00 ` Baurzhan Ismagulov
2022-02-10 8:47 ` Uladzimir Bely
2022-02-10 9:10 ` quirin.gylstorff
2022-02-11 10:54 ` Uladzimir Bely
2022-02-11 11:20 ` Jan Kiszka
2022-02-14 8:54 ` quirin.gylstorff
2022-02-14 9:47 ` Uladzimir Bely
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=818250b5-fed8-8ff9-febb-6cbf61e0680f@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=debian-user@lists.debian.org \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=josch@debian.org \
--cc=sbuild@packages.debian.org \
--cc=tobias.schmidl@siemens.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