Hi Andy, On Wed, Feb 12, 2014 at 03:29:28PM +0100, Andrew Kelly wrote: > At any rate, I'm running a farm of "stable" and "old-stable" > deployments, the dep nightmare of pulling something from testing > isn't really going to serve my customer base very well. And > the 20 minutes.. well, were it that painless I'm sure half a > dozen daily readers of this list would have already back-ported > things months and months ago.
Yeah, we did :-p We run Debian stable for our mail systems. I just build local packages for the volatile stuff like ClamAV and SpamAssassin. I guess I have to rebuild twice a year or so, and it's pretty trivial when you've done it once - copy the debian/ directory over, update the changelog and rebuild. There are very occasionally a few things that need tweaking to get it to build with the new version. Debian's policy is to ensure that stable means stable - so they only generally apply security patches. There was a "volatile" repository once as they realised that software like ClamAV needs updating more but conflicted with normal policy; it looks like it's been replaced, but I don't know if they still maintain the ClamAV package there. Cheers, Matthew -- Matthew Newton, Ph.D. <[email protected]> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <[email protected]> _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/support/ml
