|
Home > Archive > Linux Debian support > December 2005 > apt-get kde updates in Debian for unstable and testing broken for longer ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
apt-get kde updates in Debian for unstable and testing broken for longer ?
|
|
|
| It could be my wrong doing of course but ... are there people out there who
notice the current plethora of kde library / update troubles in testing and
in unstable at the moment ?
I'm running one testing and one unstable version.
It begun with an available apt-get update from kde files 4:3.4.2 -> 4:3.4.3.
that broke kde completely on an unstable system. (hence the word of course)
Now you have kig that is broken, (libboost-python problems and seemingly
multiple versions of libraries with suffixes like c2a (kde) that are
causing apt-get havoc.
Is this a 'before christmas' cleanup fest that will blow over or is the
Debian distro entering into an internal more 'unstable' period ? Forcing
perhaps people who tend to 'use' their distro to go (k)ubuntu ?
Can anybody shed some fresh light onto the current problems here ?
Thanks
David.
| |
|
| Dalo wrote:
> It could be my wrong doing of course but ... are there people out there
> who notice the current plethora of kde library / update troubles in
> testing and in unstable at the moment ?
>
> I'm running one testing and one unstable version.
> It begun with an available apt-get update from kde files 4:3.4.2 ->
> 4:3.4.3. that broke kde completely on an unstable system. (hence the word
> of course) Now you have kig that is broken, (libboost-python problems and
> seemingly
> multiple versions of libraries with suffixes like c2a (kde) that are
> causing apt-get havoc.
>
> Is this a 'before christmas' cleanup fest that will blow over or is the
> Debian distro entering into an internal more 'unstable' period ? Forcing
> perhaps people who tend to 'use' their distro to go (k)ubuntu ?
>
> Can anybody shed some fresh light onto the current problems here ?
>
> Thanks
> David.
I have looked at the loooong list returned by apt-get dist-upgrade every few
days for the past week or two ... and declined the offer to upgrade.
Here's the root-cause of it all:
http://lists.debian.org/debian-deve...1/msg00010.html
Yes, yes - a buggy allocator can cause this mighty upheaval! But imagine
all the neat new stuff that we'll find when the dust settles.
Hang in there.
| |
| Peter J Ross 2005-12-08, 5:48 pm |
| On Wed, 07 Dec 2005 23:14:29 +0100, Dalo <daloNSP@PLZibelgique.comRMV>
wrote in alt.os.linux.debian:
> It could be my wrong doing of course but ... are there people out there who
> notice the current plethora of kde library / update troubles in testing and
> in unstable at the moment ?
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 :-)
--
Nemo hibericam exspectat inquisitionem.
alt.usenet.kooks award-winners and FAQ:
<http://www.insurgent.org/~kook-faq/>
| |
|
| 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 :-)
Thank you for the info.
Of course our servers are running stable.
The laptops are running testing.
And a few 'testing' desktops are running unstable to see what's coming.
Most of the time the 'unstable' or 'testing' background is quite usuable. It
was just with all this library changes that i lost part of KDE, apt-utils
and aptitude. This was of course based upon an apt-get upgrade decision of
myself, but the sheer situation did rise questions.
How unstable can u get ;-)
In the meanwhile the unstable desktop is running normally, atp-utils and
aptitude even have their dependancies normalized now.
Whilst searching an inbetween solution is also possible by 'pinning' your
apt-get to 2 sources (testing and unstable)
This is a big solution as unison (synchronisation) is problematic is you use
stable and testing laptops. The version of unison must be the same (mostly)
Greeting,
David
|
|
|
|
|