On Tuesday, August 5, 2025 1:21:49 PM Mountain Standard Time Andrey Rakhmatullin wrote: > On Tue, Aug 05, 2025 at 04:37:50PM -0300, Leandro Cunha wrote: > >> > >> Until recently most packages required 'Rules-Requires-Root: no' be > >> > >> added to the 'debian/control' file of a package. This is no longer > >> > >> the case, with this now being default behaviour. You do not need to > >> > >> add it new packages and those maintaining packages can remove it. > >> > >> > >> > >>From what I saw here, policy 4.1.5 in 5.6.31 defined this and wouldn't > >> > > > >> > >there need to be an update to the policy about this? > >> > >https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-rules > >> > >-requires-root>> > > >> > Is there something at this link that makes you think that some update is > >> > needed or contradicts what Phil wrote? > >> > >>From what I understand, Rules-Requires-Root: no (default) would no > > > >longer be necessary. > > Yes. > > >I asked this question because it's a question I > >had, as it's listed as a default. It might lead anyone reading the > >policy to believe this would still be necessary (or not, if she/he > >sees this email). > > I don't get it, sorry. So far everything says that "no" is currently the > default and so setting it explicitly isn't needed. That is correct. The default used to be “yes”, which would cause the build environment to run as root. But only a very few packages need the build environment to run as root, and there are downsides to doing so. For a long time, you had to manually specify that a package could be build in a non-root build environment with “Rules-Requires-Root: No”. But now the default has changed. If you happen to maintain one of the few packages that does require root during build, you now have to specify “Rules-Requires-Root: Yes” in debian/control. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.