| Clinton V. Weiss 2005-12-08, 5:48 pm |
| Peter J Ross wrote:
> On Wed, 07 Dec 2005 23:14:29 +0100, Dalo <daloNSP@PLZibelgique.comRMV>
> wrote in alt.os.linux.debian:
>
>
>
>
> KDE upgrades are never easy. The solution is to "hold" your KDE
> packages until all the new versions of the software you use are
> available. The upgrade from 3.4.2 to 3.4.3 seems to me to have gone
> quite smoothly in Unstable this time. I expect 3.4->3.5 will be messy,
> as 3.3->3.4 was, and I'll have to use fluxbox, and more console apps
> than usual, for a while.
>
> Meanwhile, everything I use from KDE, including extras such as
> noteedit and rosegarden4, is now working again after only a few days.
>
>
> If you want stability, use Stable.
>
> If you don't mind having to exercise some caution before big upgrades,
> use Testing.
>
> If you're prepared to put up with stuff breaking badly in order to try
> to contribute something towards the next release, use Unstable. Note
> that more important things than KDE can break in Unstable.
>
> PJR :-)
I tend to use aptitude, which will give a score of what it is about to
do when there is a dependency mess. Last week at one point it was at
-3982, definately not good. I'll usually allow the dist-upgrade when
there is a positive number. With this method, I haven't had to stop
using KDE or any of its' programs.
Give it a shot!
Clinton
|