Looks like you probably had awstats installed from DAG before installing Virtualmin? I think I’ve added an Epoch to our package for the future, which will make DAG packages get replaced with ours (which are based on Fedora Extras, and are more likely to take the “official” party line on locations).
DAG’s repo is problematic for our installer, as we use Fedora Extras packages when available, and there are a few clashes in locations–if I force a replacement, everything works, but I don’t really like doing that. It’s just an annoying problem of having a platform that is so open and flexible (small price to pay!).
I’ll double check to be sure that the Epoch is going into the next version, so DAG’s awstats package will never over-ride ours. I might also have to force an update at the end of the installation to be sure…I don’t know.
Oh, yeah, obviously, I’d like to know if you didn’t actually have the DAG repository enabled on the box!
Actually no. The first time i installed Awstats was from the install script with Virtualmin. Since Awstats didnt work, i removed the Awstats.vm version and tried installing the rpm version from the site (awstats) and that didnt work either so i removed that too. After a couple of removing and installing i thought i should check the module config … and see what values i have on my Test Box.
Thats when i realized the different paths and changed them accordingly. Point to be noted, i installed Virtualmin on my own CentOS4.2 test box like 2 weeks ago and everything went fine awstats and all. So i would think this was on the new one. I wouldnt know though i havent tested the new installer on my test box yet.
But yeah, DAG rep is not enabled nor added to Yum. Yum is what i always use.