public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Question related to Sbuild CLEAN_SOURCE
Date: Wed, 9 Feb 2022 12:52:19 +0100	[thread overview]
Message-ID: <YgOq89OEA3YP+raB@ilbers.de> (raw)
In-Reply-To: <818250b5-fed8-8ff9-febb-6cbf61e0680f@siemens.com>

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.


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


With kind regards,
Baurzhan.

  reply	other threads:[~2022-02-09 11:52 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
2022-02-09 11:52     ` Baurzhan Ismagulov [this message]
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=YgOq89OEA3YP+raB@ilbers.de \
    --to=ibr@radix50.net \
    --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