Jim Goode wrote: > I am currently running version 0.88.7 on SME 6.0.1-01 (built on Red Hat > 7.x). > [EMAIL PROTECTED] tmp]# rpm -qa | grep clam > clamav-es-libs-0.88.7-es01 > clamav-es-0.88.7-es01
OK, so you've got a pair of packages called "clamav-es-libs" and "clamav-es". > I downloaded: > [EMAIL PROTECTED] tmp]# ls -l *.rpm > clamav-0.90.1-4.rh7.rf.i386.rpm > clamav-db-0.90.1-4.rh7.rf.i386.rpm > clamav-devel-0.90.1-4.rh7.rf.i386.rpm > clamd-0.90.1-4.rh7.rf.i386.rpm Four packages, called "clamav", "clamav-db", "clamav-devel", and "clamd". > Running: > [EMAIL PROTECTED] tmp]# rpm -Uvh clamav-db-0.90.1-4.rh7.rf.i386.rpm > clamav-devel-0.90.1-4.rh7.rf.i386.rpm clamav-0.90.1-4.rh7.rf.i386.rpm > clamd-0.90.1-4.rh7.rf.i386.rpm > > produces the following output: > Preparing... ########################################### > [100%] > file /etc/freshclam.conf from install of clamav-0.90.1-4.rh7.rf conflicts > with file from package clamav-es-0.88.7-es01 [snip almost-identical errors] > Does this mean the upgrade is not capable of taking place? Do I need to > uninstall 0.88 before installing 0.90? I've been through all the pages of > the clamav wiki and most of the archives and haven't discovered any clues to > this issue. Thanks, in advance, for whatever help you can provide, Basically, in your case, yes. Most package managers won't directly understand that a package called "foobar" replaces an older package providing the same software called "foobar-custom". Some understand a syntax in the package build process that lets the package builder say "This package replaces a package with a different name" - but it's not much help with switching from one third-party package to a package from a different source; it has to be allowed for while creating the packages. If you were *really* lucky, you *might* be able to a) force the install of the 0.90.1 .rpms, overwriting existing files and then b) tell RPM to "forget" that the old packages were ever installed. I wouldn't recommend this, it will leave bits of garbage lying around your filesystem, and will almost certainly come back to bite you in the rear at some point in the future when you least need such troubles. Because the packages have changed their layout, and there isn't a one-to-one mapping of contents, you can't even (easily) remove one package, install a package, remove the other... etc. Back up the config files (you probably won't be able to use the old ones as-is), uninstall the existing packages, install the new ones, then port your local configuration changes into the new config files. -kgd _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
