* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? Nope * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? Nope * Is the service non-persistent (i.e. run once at startup and exit)? Runs once each timer run. * What is the exact name (or names) of the systemd unit files to be enabled? sa-update.timer * Is this request for all Fedora deliverables or only for some Editions (list them)? All. See https://bugzilla.redhat.com/show_bug.cgi?id=1645826 The idea is that if you have spamassassin installed, you want the data files to be updated for other tools that call spamassassin.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Sgallagh: Can you look at this please? Or any other co-maintainers. ;)
Wow, this one really slipped through the cracks. Sorry about that. Merged to Rawhide. Do you need this backported to F32? If so, it'll need a Freeze Exception at this point.
I think rawhide is fine. It's waited this long... Thanks!
So the user who requested this would like to have it also in stable releases. Can you also do stable releases here?
FEDORA-2020-61a861a2d9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-61a861a2d9
FEDORA-2020-938393aa3c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-938393aa3c
FEDORA-2020-938393aa3c has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-938393aa3c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-938393aa3c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-61a861a2d9 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-61a861a2d9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-61a861a2d9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
So according to git, the `enable sa-update.timer` line was added a couple of months before this bug was opened: https://src.fedoraproject.org/rpms/fedora-release/c/12e91163a3c7054e1ebf4a725dc2b2fbe4fefd41 On my F31 system, with FEDORA-2020-938393aa3c installed, I see it twice: [root@normal ~]# grep -B 2 sa-update /usr/lib/systemd/system-preset/90-default.preset # https://bugzilla.redhat.com/show_bug.cgi?id=1218999 enable sa-update.timer -- # Enable regular update of SpamAssassin data files # https://bugzilla.redhat.com/show_bug.cgi?id=1651002 enable sa-update.timer [root@normal ~]# Am I missing something or is this update not going to fix the issue?
FEDORA-2020-938393aa3c has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-61a861a2d9 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.