From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Isaac True <itrue@emlix.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] debianize: set Rules-Requires-Root in debian/control
Date: Fri, 15 Aug 2025 15:39:23 +0200 [thread overview]
Message-ID: <599ab11c-7a65-46da-8643-95dd2a8c5924@siemens.com> (raw)
In-Reply-To: <13722340-f9b2-4bb0-ae49-90156c7e7087@emlix.com>
On 15.08.25 15:09, Isaac True wrote:
>>
>> Hmm, but the Policy says it's default-no anyway:
>>
>> https://www.debian.org/doc/debian-policy/ch-controlfields.html#rules-
> requires-root
>>
>> Did that default change recently?
>
> According to the deb-src-control man page (https://www.man7.org/linux/
> man-pages/man5/deb-src-control.5.html) this only became the default with
> dpkg >= 1.22.13, which is relatively recent. Anything with a dpkg
> version earlier than that (which includes Ubuntu Jammy and Noble) uses
> `binary-targets` as the default, which calls fakeroot.
>
>> This is a change that first of all requires an entry in
>> RECIPE-API-CHANGELOG.md. But you also need to explain if this is fine
>> down to buster (we still support building for it, yes, it's ELTS). And
>> you need to ensure that it will not change anything for existing layers
>> - which is in conflict with the expressed intention of this change.
>
> Understood. Would you prefer that it doesn't add the field by default in
> order to maintain backwards-compatibility, and instead only add the
> field when the value is set?
For source-based packages, we should not change the API level's default
unless explicitly requested by the recipe. So, you could add
"Rules-Requires-Root" only if DEBIAN_RULES_REQUIRES_ROOT is set e.g.
For dpkg-prebuilt, I think we can safely go to non-root but only on
those distros that already understood "Rules-Requires-Root".
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/599ab11c-7a65-46da-8643-95dd2a8c5924%40siemens.com.
next prev parent reply other threads:[~2025-08-15 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=599ab11c-7a65-46da-8643-95dd2a8c5924@siemens.com \
--to=isar-users@googlegroups.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