From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Prusty, Badrikesh" <badrikesh.prusty@siemens.com>,
Isaac True <itrue@emlix.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] debianize: set Rules-Requires-Root in debian/control
Date: Fri, 15 Aug 2025 15:44:20 +0200 [thread overview]
Message-ID: <41948f96-8cce-4bbe-9192-525351945cde@siemens.com> (raw)
In-Reply-To: <SG2PR06MB51074CAFFFE9783E0AFC72889134A@SG2PR06MB5107.apcprd06.prod.outlook.com>
On 15.08.25 15:07, 'Prusty, Badrikesh' via isar-users wrote:
> Hi,
>
> Thank you for the patch. I was about to send it.
>
> We are facing intermittent freezes with build configuration:
> ----------------------------------------------------------------------------------
> Host system: Debian Trixie
> Container image for build: kas-isar 4.8.1 (Debian Bookworm based)
> Target Build Distro: Debian-bookworm
> ----------------------------------------------------------------------------------
>
> Intermittent freezes observed during "do_dpkg_build" task when it runs the cmd: dpkg-buildpackage ----
>
Since when did you get those freezes? I'm not aware of any issues in any
of the many, many setups we have. There must be some additional variable
in play on your side.
> Debian also recommends doing non-root builds when the build process doesn't installs to system paths (e.g., /etc, /usr). That's why most packages in Debian including linux-image, firmware-nonfree use "Rules-Requires-Root: no".
>
If the upstream package in a specific debian version carries that
control field with "no" and our drop-in replacement recipe does not,
that should be fixed for that specific version. But we cannot globally
change things otherwise that easily (if at all).
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/41948f96-8cce-4bbe-9192-525351945cde%40siemens.com.
next prev parent reply other threads:[~2025-08-15 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 8:48 Isaac True
2025-08-15 13:07 ` 'Prusty, Badrikesh' via isar-users
2025-08-15 13:44 ` 'Jan Kiszka' via isar-users [this message]
2025-08-15 13:49 ` 'Prusty, Badrikesh' via isar-users
2025-08-15 14:15 ` 'Prusty, Badrikesh' via isar-users
2025-08-14 14:34 Isaac True
2025-08-15 13:01 ` 'Jan Kiszka' via isar-users
2025-08-15 13:09 ` Isaac True
2025-08-15 13:39 ` 'Jan Kiszka' via isar-users
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=41948f96-8cce-4bbe-9192-525351945cde@siemens.com \
--to=isar-users@googlegroups.com \
--cc=badrikesh.prusty@siemens.com \
--cc=itrue@emlix.com \
--cc=jan.kiszka@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