Bug 2358635 - radicale user is not created when dnf installs the package
Summary: radicale user is not created when dnf installs the package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: radicale
Version: 41
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Bieringer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-09 14:56 UTC by Dominic
Modified: 2025-04-23 02:13 UTC (History)
4 users (show)

Fixed In Version: radicale-3.5.1-2.fc42 radicale-3.5.1-3.el9 radicale-3.5.1-3.fc42 radicale-3.5.1-3.fc40 radicale-3.5.1-3.fc41 radicale-3.5.1-3.el8
Clone Of:
Environment:
Last Closed: 2025-04-11 18:30:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dominic 2025-04-09 14:56:08 UTC
When the radicale package is installed with dnf, errors are reported since the installer expects the radicale user & group to exist.

In addition, the service refuses to start, since the systemd unit is configured to run with the radicale user & group.

The fix would appear to be ensuring dnf creates the radicale user & group on installation.

Reproducible: Always

Steps to Reproduce:
1. dnf install radicale3
2. observe error output
3. systemctl start radicale.service
Actual Results:  
Errors reported by dnf, service fails to start.

Expected Results:  
No errors reported by dnf, service starts successfully on request.

Comment 1 Peter Bieringer 2025-04-09 17:02:05 UTC
thank you for reporting, introduced unfortunatly with 3.5.0-1

Fix in preinstall is on the way

@@ -385,7 +385,7 @@ rm -rf %{buildroot}%{_sharedstatedir}/%{name}/.Radicale.lock
 
 
 %pre -n %{radicale_package_name}
-%if (0%{?rhel} >= 11) || (0%{?fedora} >= 43)
+%if ! (0%{?rhel} >= 11) || (0%{?fedora} >= 43)
 getent group %{name} >/dev/null || groupadd -r %{name}
 getent passwd %{name} >/dev/null || \
     useradd -r -g %{name} -d %{_sharedstatedir}/%{name} -s /sbin/nologin \

Comment 2 Fedora Update System 2025-04-09 17:15:53 UTC
FEDORA-2025-4941999c75 (radicale-3.5.1-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4941999c75

Comment 3 Fedora Update System 2025-04-09 17:16:24 UTC
FEDORA-2025-322e2b9bfa (radicale-3.5.1-2.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-322e2b9bfa

Comment 4 Fedora Update System 2025-04-09 17:17:20 UTC
FEDORA-EPEL-2025-49be2a601f (radicale-3.5.1-2.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-49be2a601f

Comment 5 Fedora Update System 2025-04-09 17:19:15 UTC
FEDORA-2025-9ad640ad0a (radicale-3.5.1-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-9ad640ad0a

Comment 6 Peter Bieringer 2025-04-09 17:19:55 UTC
Until available in testing/stable take build from here
https://koji.fedoraproject.org/koji/packageinfo?packageID=16893

Comment 7 Fedora Update System 2025-04-09 17:20:43 UTC
FEDORA-EPEL-2025-e449fe5465 (radicale-3.5.1-2.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e449fe5465

Comment 8 Fedora Update System 2025-04-10 00:22:36 UTC
FEDORA-EPEL-2025-49be2a601f has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-49be2a601f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-04-10 02:08:59 UTC
FEDORA-2025-4941999c75 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4941999c75`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4941999c75

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-04-10 03:32:46 UTC
FEDORA-2025-322e2b9bfa has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-322e2b9bfa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-322e2b9bfa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2025-04-10 04:10:07 UTC
FEDORA-2025-9ad640ad0a has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-9ad640ad0a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9ad640ad0a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2025-04-10 04:53:36 UTC
FEDORA-EPEL-2025-e449fe5465 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e449fe5465

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2025-04-11 18:30:28 UTC
FEDORA-2025-4941999c75 (radicale-3.5.1-2.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-04-13 15:16:18 UTC
FEDORA-2025-810c85b618 (radicale-3.5.1-3.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-810c85b618

Comment 15 Fedora Update System 2025-04-13 15:16:48 UTC
FEDORA-2025-27b9e15180 (radicale-3.5.1-3.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-27b9e15180

Comment 16 Fedora Update System 2025-04-13 15:21:13 UTC
FEDORA-2025-dd71519948 (radicale-3.5.1-3.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-dd71519948

Comment 17 Fedora Update System 2025-04-13 15:23:31 UTC
FEDORA-EPEL-2025-59e4d8ce27 (radicale-3.5.1-3.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-59e4d8ce27

Comment 18 Fedora Update System 2025-04-13 15:29:04 UTC
FEDORA-EPEL-2025-bae5025627 (radicale-3.5.1-3.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bae5025627

Comment 19 Fedora Update System 2025-04-15 19:37:06 UTC
FEDORA-2025-27b9e15180 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-27b9e15180`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-27b9e15180

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 20 Fedora Update System 2025-04-15 19:52:35 UTC
FEDORA-EPEL-2025-bae5025627 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bae5025627

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 21 Fedora Update System 2025-04-15 20:21:59 UTC
FEDORA-2025-810c85b618 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-810c85b618`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-810c85b618

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 22 Fedora Update System 2025-04-15 20:28:51 UTC
FEDORA-2025-dd71519948 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-dd71519948`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dd71519948

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 23 Fedora Update System 2025-04-15 20:57:06 UTC
FEDORA-EPEL-2025-59e4d8ce27 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-59e4d8ce27

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 24 Fedora Update System 2025-04-23 00:53:54 UTC
FEDORA-EPEL-2025-59e4d8ce27 (radicale-3.5.1-3.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 25 Fedora Update System 2025-04-23 01:46:20 UTC
FEDORA-2025-810c85b618 (radicale-3.5.1-3.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 26 Fedora Update System 2025-04-23 02:00:14 UTC
FEDORA-2025-dd71519948 (radicale-3.5.1-3.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 27 Fedora Update System 2025-04-23 02:13:05 UTC
FEDORA-2025-27b9e15180 (radicale-3.5.1-3.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 28 Fedora Update System 2025-04-23 02:13:29 UTC
FEDORA-EPEL-2025-bae5025627 (radicale-3.5.1-3.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.