Hi all, I concur with this. I normally keep my system in a fairly good state of maintenance, including updating Debian stable packages. That didn't work this time, resulting in a very unstable server for days in a row (indeed I'm not a full time sysadmin, but not a first day Linux user either). I've discovered that my ISPConfig v2.3 did not contain the 0.95 clamav version, but embedded an old 0.88 version. It took a while to discover that :-(
Concluding, even with a fairly regular maintenance of my systems packages I ran into a very serious problem caused by a community decision to go for an EOL while stable Debian packages and apps like ISPConfig dating back less than a year did not provide a compatible version. Maybe it should be of concern to the developer community that there are many users out there that depend on your software (for which we are very grateful, no misunderstanding about that!) which is a key part to prevent viruses to spread via email. And I don't think one can expect all of these users to follow the community process of all key packages they depend upon. I am actively involved in FOSS development for almost ten years now, and very much aware what is involved in running a community project with developers that want to move on. I do think however that key components need more attention when it comes to EOL in cases like this. Kind regards, Jeroen > > I'm probably not fitting in the right place of the thread but I just > signed in and could not know where to start. > Our only big problem with this upgrade is that the actual debian stable > (lenny) still uses 0.94 as shipping version and one has to get volatile > sources in order to upgrade. > > That is: a fresh installation of a vanilla debian stable whould ship a > non-working unapdated clamav packet... > Should we somehow notify the debian guys the misery they're putting > they'r beloved sysadmin into? _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
