On Wed, 2005-02-09 at 08:51, Jim B wrote: > On a server is it a good idea to say once a month or every to weeks to > do a "apt-get dist-upgrade" or can that cause a world of problems? > I run `apt-get update` every couple weeks on debian testing. > Also is running testing a good idea on the one hand one would be able > to have current packages of clamav and postfix for example but can > running testing lead to an unstable machine? > This is the machine I earn my living with, and yes, updating every couple of weeks can cause problems. There is a solution though: apt-listbugs & apt-listchanges. > I want like everyone else to run the most current well working > packages for what I am using, not sure to pick unstable or testing and > is dist-upgrade safe or will it leave you in a lurch with a broken > system? > Unstable is bleeding edge. Things will break, that's why they call it "unstable". On the other hand, it gets frequent updates too. For a production machine, I would stay away from unstable. As far as testing goes, if you can afford the time to read all the bug reports and changelogs, I would (and do) use testing. Also worth mentioning, I can't run `apt-get dist-upgrade`. I have too many pinned packages (because of outstanding bugs). These pinned packages prevent enough upgrades that it tries to do things like: 55 upgraded, 50 newly installed, 461 to remove and 5 not upgraded. Without my pinned packages the 'dist-upgrade' would work as expected. I keep my system up to date with `apt-get update`. Bart --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss