https://bugzilla.redhat.com/show_bug.cgi?id=2291235
Sumit Bose sbose@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pbrezina@redhat.c | |om)
--- Comment #47 from Sumit Bose sbose@redhat.com --- (In reply to Alexey Tikhonov from comment #41)
Other candidates:
warning: fprintd-pam-1.94.2-11.fc40.x86_64 warning: -> authselect-1.5.0-5.fc41.x86_64 warning: authselect-1.5.0-5.fc41.x86_64 warning: -> fprintd-pam-1.94.2-11.fc40.x86_64
And probably most "promising":
warning: sssd-common-2.10.0~beta1-2.fc41.x86_64 warning: => systemd-256-1.fc41.x86_64 warning: -> util-linux-2.40.1-2.fc41.x86_64 warning: -> pam-1.6.1-3.fc41.x86_64 warning: -> authselect-1.5.0-5.fc41.x86_64 warning: -> sssd-2.10.0~beta1-2.fc41.x86_64
Hi,
why does authselect depend on the `sssd` meta package which will pull in everything and not only on `sssd-common`? Didn't we try to remove dependencies on the `sssd` meta package or was this only for RHEL?
Since the meta package will pull in everything it might be somewhat expected that the dependency resolver is lost and just start with some of the dependencies. If the authselect dependency would be only `sssd-common` then there is still a loop, but just with sssd-common and no other SSSD components at this point.
However, since it looks like any random component might introduce such loops I wonder what would be the alternatives to make this more reliable. One way might be using `%pretrans` another to add the `%sysusers_create_compat %{SOURCE1}` %pre macro or similar to all packages which need the SSSD user for installation. Both have the pro and cons and maybe there are others but from the given two I think I would prefer the latter.
bye, Sumit
warning: ->
sssd-common-2.10.0~beta1-2.fc41.x86_64