FEDORA-EPEL-2020-69025a53b9 created by sergiomb 10 months ago for Fedora EPEL 7
obsolete
  • More cleanups
  • Remove llvm-glibc.patch (upstream already fixed it)
  • Comment "Example" in scan.conf to make clamd@scan.service to have less to editing
  • Improve description of clamav-update

  • Fix systemd scriptlets

  • Improve upgrade path

  • Get rid of pkgdatadir variable
  • Use upstream freshclam systemd unit file, remove freshclam-slee
  • Get rid of %freshclamlog variable
  • Get rid of smartsubst function

  • Fix scriplets (#1788338)

  • Delete unused files

  • Remove old init scripts and use only systemd

  • Still need some work at least add freshclam unit

  • Allow building --with unrar again (bz#1782638)

This update has been submitted for testing by sergiomb.

10 months ago

This update's test gating status has been changed to 'waiting'.

10 months ago

This update's test gating status has been changed to 'ignored'.

10 months ago

This update has been pushed to testing.

9 months ago
User Icon robert commented & provided feedback 9 months ago
karma

Introducing clamav-freshclam.service without an automagic upgrade path breaks existing unattended installations. Please introduce a proper %post scriptlet for this. And why is it called clamav-freshclam.service rather freshclam.service?

Test Case ClamAV

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

9 months ago

no , do is not clamav-freshclam.service just starts if cron.d is not present and freshclam.conf works at same way , just need do systemctl enable clamav-freshclam.service . We use upstream as is i.e. clamav-freshclam.service anyway pull requests or code that you are thinking is welcome

User Icon robert commented & provided feedback 9 months ago
karma

As of clamav-update-0.101.5-7.el7, there is no more cronjob (while it existed at clamav-update-0.101.5-1.el7). It is IMHO not acceptable for existing RHEL/CentOS systems to change a package that drastically, that systemctl enable clamav-freshclam.service gets suddenly mandatory while it was previously not. System administrators of RHEL/CentOS systems expect that running yum update without further interventions keeps the system running and the configuration unchanged.

Test Case ClamAV

sergiomb edited this update.

9 months ago
User Icon sergiomb commented & provided feedback 9 months ago

Red Hat Enterprise Linux 7.0 was released 10 de junho de 2014, freshclam unit systemd bug report was opened on 2012, I'm just trying to fix the BZ#801994 "freshclam (clamav-update) does not integrate with systemd or SYSV sysinit at installation" . This is the last drastic modification of clamav for el7 , if clamav itself does not changed drastically . What else could I do ?

User Icon sergiomb commented & provided feedback 9 months ago

"systemctl enable clamav-freshclam.service gets suddenly mandatory while it was previously not" as was mandatory edit freshclam.conf to enable freshclam updates to allow use internet . "Please introduce a proper %post scriptlet for this. " what do you suggest ? a big fat warning freshclam moved to systemd please run systemctl enable clamav-freshclam --now to enable updates ?

User Icon leejnk commented & provided feedback 9 months ago
karma

Working Fine on Centos 7.7.

BZ#801994 freshclam (clamav-update) does not integrate with systemd or SYSV sysinit at installation
Test Case ClamAV
User Icon orion commented & provided feedback 9 months ago
karma

I agree that dropping the old cron based update mechanism is not okay in EPEL7. It's not the same as having to have edit freshclam.conf - that was done once when clamav was first installed. This breaks running systems. Please re-add it.

User Icon sergiomb commented & provided feedback 9 months ago

The commit is here [1] %_sysconfdir/logrotate.d/ , %_sysconfdir/cron.d/clamav-update, %_sysconfdir/sysconfig/freshclam are configured with %config(noreplace) . I don't understand how we can make new users use the systemd unit if we keep a bunch of files that should have been removed a long time ago, we don't need any file because upstreamed systemd unit do it all in standard way of systemd. But let's open a ticket to decide what to do , in the several branches . and anyway I'm adding a warning to do the simple comand that fixes it all systemctl enable clamav-freshclam --now

[1] https://src.fedoraproject.org/rpms/clamav/c/c162cace14ff84128aa2b15523d16282eceb5d6b?branch=master

User Icon sergiomb commented & provided feedback 9 months ago

The commit is here [1] %_sysconfdir/logrotate.d/ , %_sysconfdir/cron.d/clamav-update, %_sysconfdir/sysconfig/freshclam are configured with %config(noreplace) .
I don't understand how we can make new users use the systemd unit if we keep a bunch of files that should have been removed a long time ago, we don't need any file because upstreamed systemd unit do it all in standard way of systemd.
But let's open a ticket to decide what to do , in the several branches .
Anyway I'm adding a warning to do the simple comand that fixes it all:
systemctl enable clamav-freshclam --now

[1] https://src.fedoraproject.org/rpms/clamav/c/c162cace14ff84128aa2b15523d16282eceb5d6b?branch=master

This update has been obsoleted by clamav-0.101.5-9.el7.

9 months ago
User Icon orion commented & provided feedback 9 months ago

Please login to add feedback.

Metadata
Type
bugfix
Severity
medium
Karma
-1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
10 months ago
in testing
9 months ago
modified
9 months ago
BZ#801994 freshclam (clamav-update) does not integrate with systemd or SYSV sysinit at installation
0
1

Automated Test Results

Test Cases

-1 1 Test Case ClamAV