public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
	Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: "Gylstorff, Quirin (FT RPD CED OES-DE)" <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH] dpkg: Configure sbuild for schroot
Date: Wed, 15 Apr 2026 16:10:55 +0200	[thread overview]
Message-ID: <40f19faa-39dd-498b-8100-b409d7cc8ff5@siemens.com> (raw)
In-Reply-To: <5c26019c-ff46-4c35-94b7-7e3a8046fb1d@siemens.com>

On 15.04.26 16:04, 'Jan Kiszka' via isar-users wrote:
> On 15.04.26 15:56, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
>> On Wed, 2026-04-15 at 14:50 +0200, 'Jan Kiszka' via isar-users wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> This is what at least the trixie version of sbuild strongly recommends
>>> and also what the forky version will require.
>>>
>>> $chroot_mode is known to sbuild buster at least. It remains unclear when
>>> $schroot was introduced, but it was very likely ignored before that. So
>>> this changes is backward-compatible with older builders.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> ---
>>>
>>> Tested with a local experimental kas-isar forky container.
>>>
>>>  meta/classes-recipe/dpkg.bbclass | 2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>> diff --git a/meta/classes-recipe/dpkg.bbclass b/meta/classes-recipe/dpkg.bbclass
>>> index c1c38184..24eb0f7e 100644
>>> --- a/meta/classes-recipe/dpkg.bbclass
>>> +++ b/meta/classes-recipe/dpkg.bbclass
>>> @@ -106,6 +106,8 @@ dpkg_runbuild() {
>>>  
>>>      echo '$apt_keep_downloaded_packages = 1;' >> ${SBUILD_CONFIG}
>>>      echo '$stalled_pkg_timeout = ${DPKG_BUILD_TIMEOUT};' >> ${SBUILD_CONFIG}
>>> +    echo '$chroot_mode = "schroot";' >> ${SBUILD_CONFIG}
>>> +    echo '$schroot = "schroot";' >> ${SBUILD_CONFIG}
>>
>> This should not be required (since [1]), as we select the chroot mode
>> when calling sbuild [2]. That's also compatible with the rootless
>> series where we just select unshare.
>>
>> [1]https://github.com/ilbers/isar/commit/fec8600fea2ca741373c9e3e4f3d41f147dfbb09
>>
> 
> Indeed, I tested with an older Isar baseline and didn't notice this
> switch while forward-porting. Let me double-check with 1.0-rc1 again if
> the issue under forky is gone.
> 

And it does work, of course - so please ignore this.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/40f19faa-39dd-498b-8100-b409d7cc8ff5%40siemens.com.

      reply	other threads:[~2026-04-15 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 12:50 'Jan Kiszka' via isar-users
2026-04-15 12:56 ` 'Jan Kiszka' via isar-users
2026-04-15 13:56 ` 'MOESSBAUER, Felix' via isar-users
2026-04-15 14:04   ` 'Jan Kiszka' via isar-users
2026-04-15 14:10     ` 'Jan Kiszka' via isar-users [this message]

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=40f19faa-39dd-498b-8100-b409d7cc8ff5@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@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