Re: [rfc] mass package change to introduce sysusers.d configs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 24, 2025 at 07:44:31PM +0100, Tomasz Torcz wrote:
> On Fri, Jan 24, 2025 at 02:07:07PM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> > On Fri, Jan 24, 2025 at 08:55:12AM +0000, Peter Robinson wrote:
> > > On Thu, 23 Jan 2025 at 20:52, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
> > > wrote:
> > > Is there a list of those packages?
> > 
> > > > The first batch:
> > > > https://in.waw.pl/~zbyszek/fedora/sysusers_mass_spec_change_v1.diff.html
> > 
> > ^ Those are the ones I have patches ready for so far.
> > maradns
> 
>  MaraDNS' .spec gets UID/GID of freshly created user to update the configfile:
>  https://src.fedoraproject.org/rpms/maradns/blob/rawhide/f/maradns.spec#_121-139

The %post scriptlet should continue to work without changes.

> How this would work with sysusers? I thought sysusers:
> – only support staticly allocated UIDS/GIDS

systemd-sysusers allows two of the allocation approaches described in [1]:
- dynamic, where the uid/gid numbers are not specified and are
  selected from the allowed range
- soft-static, where the uid/gid numbers are given, and will be used
  if available, and if already taken, a different number will be
  selected.

[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/

> – are run after the RPM installation.

The new mechinism in rpm itself creates the accounts _before_ the rpm
is installed. (When the rpm is being built, if it has a sysusers file,
a virtual Provides is generated. When rpm sees an rpm with the Provides,
it will precreate the account.)

So yeah, having a package with a sysusers file and files owned by the
users or groups defined therein works fine. (This was already possible
before, but required careful creation of a %pre scriptlet. The new
mechanism is much nicer.)

Zbyszek
-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux