Managing Backports and Package Updates With Sarge

Posted by a3ulafia on Wed 1 Mar 2006 at 10:38

I stick to the mantra that the stable branch is for production servers and unstable/testing is only for people who know how to fix things when they break or can afford to take a box offline. But stable gets old fast. Its security updates are only for issues that effect, well, security and not application stability.

For example, there was a recent update to the Asterisk PBX with many Changelog entries fixing memory leaks. This is not a security issue but is most definitely a stability one.

For my production servers running Asterisk, this is an essential update.

Short of packaging all updates to a package oneself, what kind of backport strategy do you use?

Where are good places to go to get updated packages or to work with other people doing the same kind of work?


This article can be found online at the Debian Administration website at the following bookmarkable URL:

This article is copyright 2006 a3ulafia - please ask for permission to republish or translate.