Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have GNU/Linux Debian Servers (Etch/Lenny) in production. I want theses systems to stay up to date. I have installed apticron with tells me what packet needs an upgrade. What is the good practice for production servers and stable releases of debian:

  • always upgrade all packets (risky or not on debian stable?) OR
  • only apply security updates (enough or not?)

Thanks!

share|improve this question

4 Answers 4

up vote 5 down vote accepted

once you got a Debian stable release installed (etch,for your example) you will not have anything but security fixes to install. Debian's policy is not to change/upgrade the softwares within a given release but just provide a fix for problems which has been discovered between two releases.

by the way, I wouldn't let anything do the upgrade but myself. A malformed install/init script will make your system unavailable in a minute, therefore you can and shall use download helpers, but do not let the upgrade process go unsupervised.

share|improve this answer
    
The point is what you are naming "a release", debian makes updates inside the same Major release (say Lenny for example), updating it from initial version to r1, r2 and so on. –  AlberT Aug 12 '09 at 10:46
1  
the bug fixes are done by patches maintaining the same program version over the given (for example, etch) release. when a stable distribution gets old, security fixes are applied on the installation media (install dvds, cds), re-releasing them then incrementing r. Current release is 5.0.2 which is lenny r2. The next debian distribution will be called Squeeze r0 –  asdmin Aug 12 '09 at 13:09

I usually make every update on the stable branch, no problems for years and years even passing from a release to another.

My servers live with a daily, manually run, upgrade-system (great tool) and they have been updated and upgraded from Woody to Lenny quite simply.

Of course I do not make the updates via cron, I get only the updates availability this way.

In case of core packages such as glibc I first test the update on a non production machine, of course.

PS: I strongly recoment upgrade-system, as it runs deborphan too and helps to keep the system up to date and clean at the same time

My 2 cents

Edit:
Note that inside a given release (Lenny for examples), could perfectly be a "sub-release", say 5.0-r1, 5.0-r2 and so on. alt text

As reported in the wikipedia page on Debian, a stable release can be updated to fulfill security and/or usability issues:

"stable, presently aliased lenny, is the current release that has stable and well tested software. Stable is made by freezing testing for a few months where bugs are fixed in order to make the distribution as stable as possible; then the resulting system is released as stable. It is updated only if major security or usability fixes are incorporated."

The short answer to asdmin's opposition is that it is perfectly possible to have non security related updates even inside the same major stable release

share|improve this answer
    
Thanks for the upgrade-system flag, but you could get away with using aptitude for the same idea. –  David Rickman Aug 12 '09 at 9:18
    
aptitude is much more interactive, upgrade-system instead makes everything needed just running it. de gustibus non disputandum est, of course :) –  AlberT Aug 12 '09 at 9:47
    
debian will not ship new softwares for stable distributions between 2 releases. all new packages will be security fixes on the same versions –  asdmin Aug 12 '09 at 10:12
    
@AlberT, of course. –  David Rickman Aug 12 '09 at 10:14
    
about updates on usability issue: at debian, usability issue is not about cosmetics. most of the time, even from the highest demand from debian community, the release will stand, even it's not quite usable (see php+gd problem). btw it's the major reason why the freezing time is usually so long –  asdmin Aug 12 '09 at 13:17

In this similar question there's an answer pointing to the very promising apt-dater program, where you can manage updates and install packages from a central location with a ncurses interface.

share|improve this answer
    
I didn't known about apt-dater, it seems good. Will try it. +1 –  AlberT Aug 13 '09 at 9:33

I have started using cron-apt after I asked a similiar question and have found it to be quite useful.

Cron-apt downloads the updates and can send an e-mail when there are new differences so that you can manually upgrade.

I currently have it set up so that it checks for new updates every night and mails me the when there are new updates to be installed.

I only download and install updates for stable packages and usually do a short check on the release notes (if any) so that I know what I am actually upgrading.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.