+++ This bug was initially created as a clone of Bug #2095372 +++ Description of problem: bind is using static useradd scripts Version-Release number of selected component (if applicable): bind-9.16.23-3.el9.src.rpm How reproducible:100% Steps to Reproduce: 1.review %post 2. 3. Actual results: %pre if [ "$1" -eq 1 ]; then /usr/sbin/groupadd -g %{bind_gid} -f -r named >/dev/null 2>&1 || :; /usr/sbin/useradd -u %{bind_uid} -r -N -M -g named -s /sbin/nologin -d /var/named -c Named named >/dev/null 2>&1 || :; fi; :; Expected results: use of system-sysusers Additional info: https://www.freedesktop.org/software/systemd/man/systemd-sysusers.html https://fedoraproject.org/wiki/Changes/Adopting_sysusers.d_format --- Additional comment from Petr Menšík on 2022-06-10 17:28:08 CEST --- Is there any use case, which would be solved by this change? --- Additional comment from Pat Riehecky on 2022-06-10 17:34:12 CEST --- Mostly it was just me noticing things out of sync with the current fedora guidelines. If you want to fix it up there and wait for RHEL10 I'm fine with that.
Okay, since I got request changing this: https://src.fedoraproject.org/rpms/bind/pull-request/32 This has increased priority now. I think it is time to switch it finally with upcoming change. https://fedoraproject.org/wiki/Changes/RPMSuportForSystemdSysusers
FEDORA-2025-4133095c61 (bind-9.18.33-1.fc43 and bind-dyndb-ldap-11.11-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4133095c61
FEDORA-2025-8033aca0a2 (bind-9.18.33-1.fc42 and bind-dyndb-ldap-11.11-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8033aca0a2
FEDORA-2025-4133095c61 (bind-9.18.33-1.fc43 and bind-dyndb-ldap-11.11-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-8033aca0a2 (bind-9.18.33-1.fc42 and bind-dyndb-ldap-11.11-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.