Bug after todays update?

[claydoh]

Re: Bug after todays update?

Not necessarily, as breakages can and WILL happen frequently, and even daily to different parts of the system until they lock everything down. Later beta releases, and perhaps even the rc's are a better bet.

[GreyGeek]

Re: Bug after todays update?

.....
I would assume that it could be abit more stable with the Alpha2 planned at jan. 16th(?)

You could assume that ... but it would not change the fact that Lucid is still in alpha, which means that no assumptions are valid and no guarantees are given. If you run alphas OR betas the RULE is to expect things to break.

I ran Jaunty from Alpha 4 through to the rollout. The development process was unusual in that it was remarkably smooth throughout that period for MY notebook. In fact, Jaunty's Alpha4 was the FIRST Linux LiveCD that I tried which could set up a 3D accelerated video out of the box. None of the other distros I tried in the preceding 6 months could give anything other than a VESA screen. I originally tried Jaunty because it was the first to advertise the KDE 4.2 desktop and I wanted to try it. Getting 3D accelerated video was totally unexpected because I had been running Mandriva 2009 PWP for the previous 6 months and was working with the xorg developers on the black screen problem that my GM45 video chip presented. The solution was found in the middle of last February and the solution was expected to trickle down to the distros for at least two or three months. The reason Jaunty gave me accelerated video in the last week of February when Mandriva did not was, I discovered, due to the fact that Jaunty's HAL "decided" that the i915 video driver was what my GM45 chip needed. On Mandriva HAL "decided" that the i810 driver was the one to use. That was the driver I filed the bug report on and was working with the xorg crew to resolve. This is also a good object lesson for those who believe that Linux would be "better off" putting all of its eggs in one basket.

[3vi1]

Re: Bug after todays update?

Not necessarily, as breakages can and WILL happen frequently, and even daily to different parts of the system until they lock everything down. Later beta releases, and perhaps even the rc's are a better bet.

True dat. I've been playing with every Kubuntu alpha for the last couple of years, and pretty much every one of them has seen multiple days where the repos were in a condition that will leave your machine "in a bad way" if you were to blindly upgrade (even at beta, occasionally).

I consider those days "learning opportunities".

[3vi1]

Re: Bug after todays update?

...Amarok-common is broke for me...

Amarok-common is actually fine, but you are correct - The main amarok package has issues: it appears to have failed to build for certain architectures due to the state of KDE in the repositories. Looks like the build system couldn't get libplasma3, libkcddb-dev, and kdemultimedia-kio-plugins

http://launchpadlibrarian.net/376258...TOBUILD.txt.gz

If you update amarok-common right now, it will remove your main amarok package (because that package needs the exact version of amarok-common you're replacing). And, you won't be about to re-install amarok, because the co-requisite version of amarok-common is not in the repository. Long story short, don't do it!