Your email got here just a little while after I finished finding the same thing (after several hours of looking) and coming up with a similar solution! Thanks for confirming my understanding of the problem! I had been wondering why I wasn't getting any updates when I keep seeing announcements of updates. I wounder how many other things in logwatch are broken that we aren't seeing? I just installed CentOS a few weeks ago and am still learning about this distros' methods and such, but I vote for sending out a patch or fixed package for it. There is no sense publishing known broken code when it isn't likely that the upstream isn't going to do anything about it. On Saturday 24 December 2005 11:00 pm, Aleksandar Milivojevic wrote: > Don't remember if I already wrote about this. But ran into it tonibhg > again. Logwatch as distributed with CentOS expects yum log files in > different format. As result, logwatch will not report anything. > > The patch is really simple (and attached). Hopefully it'll be part of > 4.3 (if not sooner). The upstream is not likely to patch it, since they > don't distribute yum at all. Maybe upstream's upstream, but than we'd > have to wait for upstream to have reason to uply upstream's upstream > change ;-) > > I guess it's kind of bordercase. But since it applies to something > where upstream and CentOS are different anyhow, maybe it is OK to > introduce this change.