From: "'Prusty, Badrikesh' via isar-users" <isar-users@googlegroups.com>
To: "Prusty, Badrikesh" <badrikesh.prusty@siemens.com>,
"Kiszka, Jan" <jan.kiszka@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 14:15:19 +0000 [thread overview]
Message-ID: <SG2PR06MB51075693AC46BF58ED408DBD9134A@SG2PR06MB5107.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <SG2PR06MB5107B8CF65C57DBB9950EE6E9134A@SG2PR06MB5107.apcprd06.prod.outlook.com>
Note: The system is not that fast-just a basic workstation:
CPU: Intel(R) Core(TM) i7-6700 (4Core / 8Thread)
HDD: Gen-3 SATA SSD
RAM: 32 GB
However, I didn't observe any freezes in the following scenarios:
1. Host: Trixie, Container: kas-isar 4.8.1 (Bookworm), Target Distro: debian-trixie (native/cross builds)
2. Host: Bookworm, Container: kas-isar 4.8.1 (Bookworm), Target Distro: debian-bookworm (native/cross builds)
Freezes were only observed in the scenarios mentioned in earlier comments.
Badrikesh
-----Original Message-----
From: 'Prusty, Badrikesh' via isar-users <isar-users@googlegroups.com>
Sent: 15 August 2025 19:19
To: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com>; Isaac True <itrue@emlix.com>; isar-users@googlegroups.com
Subject: RE: [PATCH] debianize: set Rules-Requires-Root in debian/control
Hi Jan,
Tested buster builds as well, build configuration:
----------------------------------------------------------------------------------
Host system: Debian Trixie (Debian version: 13.0, kernel: 6.12.41+deb13-amd64) Container image for build: kas-isar 4.8.1 (Debian Bookworm based) Target Build Distro: Debian-buster Target machine: qemuamd64 Target image: isar-image-base
----------------------------------------------------------------------------------
The build starts to intermittently freeze starting from this point:
```
tail -f build/tmp/work/debian-buster-amd64/samefile/2.14-r0/temp/log.do_dpkg_build
-----------------
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package samefile
dpkg-buildpackage: info: source version 2.14
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Unknown maintainer <unknown@example.com> dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean ```
As a result, these can take 40-45 minutes to build.
With the changes as done here in the patch: along with other files:
meta/classes/debianize.bbclass
meta/recipes-kernel/linux-module/files/debian/control.tmpl (build freezes: as isar-image-base requires example-module-amd64)
Thanks,
Badrikesh
-----Original Message-----
From: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com>
Sent: 15 August 2025 19:14
To: Prusty, Badrikesh (FT FDS CES LX PBU 2) <badrikesh.prusty@siemens.com>; Isaac True <itrue@emlix.com>; isar-users@googlegroups.com
Subject: Re: [PATCH] debianize: set Rules-Requires-Root in debian/control
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/SG2PR06MB5107B8CF65C57DBB9950EE6E9134A%40SG2PR06MB5107.apcprd06.prod.outlook.com.
--
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/SG2PR06MB51075693AC46BF58ED408DBD9134A%40SG2PR06MB5107.apcprd06.prod.outlook.com.
next prev parent reply other threads:[~2025-08-15 14:15 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
2025-08-15 13:49 ` 'Prusty, Badrikesh' via isar-users
2025-08-15 14:15 ` 'Prusty, Badrikesh' via isar-users [this message]
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=SG2PR06MB51075693AC46BF58ED408DBD9134A@SG2PR06MB5107.apcprd06.prod.outlook.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