Bug 155812 - rpm conflict with clamav
rpm conflict with clamav
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jiri Ryska
Depends On:
  Show dependency treegraph
Reported: 2005-04-23 15:59 EDT by Zenon Panoussis
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-26 10:33:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zenon Panoussis 2005-04-23 15:59:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050417 Fedora/1.7.7-1.3.1

Description of problem:
Attempting to update 5.2.2-1 with 5.2.2-1.FC3 using up2date fails due to a conflict about /etc/log.d/conf/services/clamav.conf, which is owned by the clamav package. 

clamav is not part of the official FC3 distribution, so FC3's logwatch should not contain/claim its files. 

As an aside, yum had no problems with this; it just went right on and made a mess:

Downloading Packages:
(1/1): logwatch-5.2.2-1.F 100% |=========================| 140 kB    00:01
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating: logwatch 100 % done 1/2
Completing update for logwatch  - 2/2

Updated: logwatch.noarch 0:5.2.2-1.FC3

# rpm -qf /etc/log.d/conf/services/clamav.conf

I guess taht's a different bug...

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:
1. Install the clamav rpm from clamav.net
2. Use up2date to update logwatch


Additional info:
Comment 1 Jiri Ryska 2005-04-26 10:33:47 EDT
This is not a bug of logwatch (especially against package not provided by
RedHat), but bug of clamav. Btw, the latest clamav (clamav-0.83-1) solves this

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