From 6e8f511e4bf0f9d55c02462696f7cbd4aeb6679a Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Wed, 9 Dec 2020 13:12:10 -0800 Subject: [PATCH] Add fprintd-pam to a new critical-path-standard group We had a situation with an fprintd update that broke su and console logins: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f997de7d0e so clearly fprintd should be on the critical path. This is my best guess as to how we should best do this (will discuss details in the PR). Signed-off-by: Adam Williamson --- comps-f32.xml.in | 1 + comps-f33.xml.in | 1 + comps-f34.xml.in | 11 +++++++++++ 3 files changed, 13 insertions(+) diff --git a/comps-f32.xml.in b/comps-f32.xml.in index 6f990c1d..a3bad4b6 100644 --- a/comps-f32.xml.in +++ b/comps-f32.xml.in @@ -686,6 +686,7 @@ dbus-broker dnf dracut + fprintd-pam gcc-c++ initial-setup + <_description>A set of packages that relate to Critical Path functionality and are in standard but not base + false + false + + fprintd-pam + + critical-path-xfce <_name>Critical Path (Xfce)