On 7/2/2013 5:18 PM, Pete Geenhuizen wrote:

On 07/02/2013 04:02 PM, Adrian P. van Bloois wrote:

...

Hi, What happened to dag.wieers? There is an update for clamav but the rpm is still not distibuted after 4 weeks or more. :-) What's wrong there?

Adrian

I asked about clamav on the repoforge list, and apparently there are some longstanding on-going issues with rpmforge, not sure exactly what and that apparently for quite some time some people have been attempting to resolve them.

Due to the length of time that these problems have existed there's also a fair amount of skepticism that the issues will be resolved.

There are several suggestions on how to resolve the clamav issue, one of them was to use the version from epel which is what I opted to do. Depending on your point of view I found it to be a relatively easy switch, just had to deal with a few ownership issues.

All in all it's a shame that there are issues as I've used rpmforge for years and have been pleased with the repo.

Pete

I very much liked the rpmforge repo for many years. However, clamav was one that I wasn't so happy with from them. It seems the username would switch back and forth from clam to clamav to clam to clamav and I would have a non-working version which I didn't always know about. (log file wrong user permission problems)

I switched the clamav install to epel and have had flawless success with their packaging. It's easy to do excludes for various repos so that you don't get conflicting installations.

Rpmforge and Daz have done great work and I'm not meaning for this to sound negative. It was just this one package. Maybe it was two packagers switching the username depending on who did the update? I don't know.

John Hinton

On Tue, Jul 2, 2013 at 4:55 PM, Tilman Schmidt t.schmidt@phoenixsoftware.de wrote:

I only experienced that when a system inadvertently switched between RPMforge and EPEL because I hadn't set up the excludes properly and the one I didn't want to use updated to a new ClamAV version before the other one.

AFAIR RPMforge has always used user "clamav", and EPEL user "clam".

I've run into a few things over the years where I first used the rpmforge version because a package wasn't in epel, then had it show up in epel with the same name and a different configuration so they'd break when the updates leapfrog each other. Viewvc is the other one that comes to mind.

-- Les Mikesell lesmikesell@gmail.com