Hide Forgot
Description of problem: EL7 is very much at the stable point in its life. It is not appropriate at this point to break running systems and force them to switch to the clamav-freshclam.service. Keep the existing cron job in place for the remaining life of EPEL7. Messages in %post are insufficient as well because they may not be seen by a human. Version-Release number of selected component (if applicable): clamav-0.101.5-9.el7
Sérgio, this bug is exclusively yours: You broke it, you fix it ;-) Please revert to a cronjob for the lifetime of RHEL/CentOS 7.
OK , you win by vote , I will revert it , for 1.102.1 update , I'm in a place with limited internet right now .
But please mark cron script as %config (it it is not so already).
yeah to be able to disable cron and use systemd ? guys, after 2 weeks if freshclam doesn't run they have a new warning and they just have to do `systemctl enable clamav-freshclam --now` (the freshclam.conf is the same) , I don't see the drama ,and this is something that should have been done in 2012 , all new installations will benefit with it . Anyway I'm complete under water , please be patient ...
https://src.fedoraproject.org/rpms/clamav/pull-request/9 The cron job has been fine for years and there is no great benefit to the freshclam service, so there is no reason to break existing installs. If users want the new service they can comment out the line in /etc/cron.d/clamav-update and enable clamav-freshclam. But they can do this on their own schedule without having it be a surprise.
FEDORA-EPEL-2020-b1621119f6 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b1621119f6
clamav-0.101.5-10.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b1621119f6
> and this is something that should have been done in 2012 yeah if you would have done it in 2012 and within a Fedora *Rawhide* instead in the middle of a GA release it wouldn't be a topic now in 2020 and never been von RHEL7 but all our your packaging change shere and there in the past months dive me crazy! i have my f**ng update-unit in place and all your removal of /etc/sysconfig/freshcal, restore it again, switch to a service, spit a cronjob again into /etc/cron.d which got enabled everywhere because of the removal of /etc/sysconfig/freshclam leaded to a ton of headache, errors and OOM killers here instead of change packaging in the middle of releaes better invest your time to keep up with updates instead doing cosemtic changes and have the users see warnings twice per hour about outdated software itself you clearly violate packaging guidelines repeatly instead doing the real important stuff
> i have update-unit in place and all your removal of /etc/sysconfig/freshcal, restore it again, switch to a service, spit a cronjob again into /etc/cron.d which got enabled everywhere because of the removal of /etc/sysconfig/freshclam leaded to a ton of headache, errors and OOM killers here yeah sorry my mistake the package in question doesn't hit updates-testing ( thank you for the report ) and was fixed one hour later . as I wrote in the other bug report, I did a mistake and instead [2] I put [1]. Let's try not lose our time with argumentation . [1] %if 0%{?fedora} && 0%{?rhel} >= 8 %bcond_with old_freshclam [2] %if 0%{?fedora} || 0%{?rhel} >= 8 %bcond_with old_freshclam
clamav-0.101.5-10.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.