Following the remarkably successful launch of the KDE 3 series with
a very stable KDE 3.0 last month,
the KDE Project today announced the immediate availability of KDE 3.0.1.
While primarily a translation release, it also squashes some bugs, including
some minor security issues with KHTML. Check out theannouncement and the fairly completeChangeLog.
Binary packages are available from the stalwart KDE packagers at
Compaq Tru64, Conectiva Linux, Mandrake Linux and SuSE Linux.
As always, we hope you enjoy the latest and greatest KDE!

check calc.cx/kde.txt ! They have had debs ready for a month and they were just about to put it into sid, but now they have changed their mind and are PLANNING ON WAITING ANOTHER MONTH for GCC3.1 to become the standard compiler. Apparantly they have lost touch with normal users that actually do use the standard debian-archives.

The alternative is bumping the soname when gcc-3.1 comes in (in the next week or two, I'm told), and fucking things up. Deal for a week or so, or you can deal with co-ordinating recompiling Qt, KDE, all the packages that depend on KDE, and so on, and so forth ...

With respect to the most popular KDE compiler, gcc/egcs, please note that some components of KDE will not compile properly with gcc versions earlier than gcc-2.95, such as egcs-1.1.2 or gcc-2.7.2, or with unpatched versions of gcc 3.0.x. However, KDE should compile properly with gcc 3.1, provided that neither debugging support nor strict syntax checking is enabled.

i'm lost in RedHat's handling of KDE. no 3.0.1 packages (maybe they'll be there in a few days), and, moreover, KDE 3 was shipped heavily patched in RH 7.3... kdelibs is numbered kdelibs-3.0.0-10. what does it fix precisely ? what is not fixed and fixed in 3.0.1 ? is it just redhat-specific patches ? nobody knows.
maybe a long digging of the sources should reveal that to the world ;-))

To find out what patches were applied to the RH7.3 packages, simply install(not build) the src RPM. There should be a bunch of patches applied in the SPEC file script(the patches themselves are probably in the BUILD directory). Source RPMs should always come with a copy of the pristine source as released along with any patches that were applied separately.

Also I would be surprised, no amazed, if Bero(who builds the RH packages alone AFAIK and does a great job of it) did not contribute any generally useful patches(i.e. not RH specific) back to the main KDE tree.

the problem is that, starting from kde3, each app has now a separate RPM, but apparently, they still come from the same SRPMS as before... so for most of the apps, the patchlevel of the RPM is simply misleading.

but i'll have a look. and i still hope that RH will release 3.0.1 RPMs ;-)

i know this. but i'll never used fresh RPMs from bero once again. last time i did it, he compiled KDE 2.2.2 against qt 2.3.2, as there was a clear "don't do that" from the KDE team. it resulted as the buggiest KDE i've ever used (clipboard was messing everything) ;-)

moreover, i wonder what "kde 3.1.0" is... did i miss any announcment ;-))

> Speaking of bugs... Why does the number of bugs seem to get bigger and bigger:

That`s a natural thing: More users, more bug reports. And most bugs get more than one report, most noticeable with khtml, and it needs much work to identify duplicates. What I found interesting when reading http://www.linux.org.uk/~telsa/Trips/Talks/g3-bugzilla.html is that Gnome "receives one hundred to three hundred bugs a day." Make your own conclusion if there are more (native english-speaking) users, automated crash reports(?) or just more bugs. Anyway don`t wonder they can close up to 300 bug reports between every Beta release.

1) more users mean more bugs found and more reports made on the same bugs
2) more code means more bugs to be found (looks at how much more there is in kde now than there was in the kde1 days)
3) developers can use a hand closing duplicates and closing non-reproducable bugs
4) all the same, the number of bugs isn't growing out of control and KDE remains very stable

the fact that the number of bug reports (including wishlist items) is growing is a sign that kde itself is growing.

There was some idea a while back that after some time after an updated release a mail would be sent to the person (for each unclosed bug report) that sent the bugreport asking him if it has been fixed.

Ofcourse a mail with all bugs reported by the user would be sent. If he never replies to the mail the reports will be closed after a certain amount of time.

This would kill some of the very old and hopefully not ligitimate bugs.

yep, i know that, and i actually do it for some apps (kwintv, kyim, ...). but then, if i start to do it for such a big thing as KDE, why use a distro and not LFS ?
moreover, my comp is an old Celeron 450 (overclocked), and it takes hours to compile anything on it, so, for the whole KDE, i have the feeling it'll die ;-)
i think the only option for me is switching the distro. i'm considering to do it more and more....

With my old Duches 400 (No overclocking 398 to be exact) I used about 24hrs
on the base packages + network and multimedia (3.0 beta 2 or 3). The bad one
is Qt on 6-7 hrs. You can save some time (several hrs) compiling Qt without tutorials and example code :)

Yes, I agree on this one.
RedHat always make it a pain with new KDE releases.
That's why I don´t use RedHat anymore.
I suggest you choose another distro as well,
it makes it a lot easier. I've always
been happy with Mandrake.

I am sure they will compile the packages. They have always done it for stable releases. It usually takes a couple more days for the Red Hat packages, but it is all right. Please remember folks, IT IS HARD to make money with GPL code. It is not impossible, but it is hard. They are doing their best. Please BE POLITE in your requests. We need (worldwide) more companies like Red Hat, Suse , Mandrake, etc, and less companies like ... you know, M$.

I am sure they will compile the packages. They have always done it for stable releases.

erm no, not _at_all_ !!!
in RH 6, KDE1 wasn't even included. that's how Mandrake started: a RH with KDE1, and compiled for i586 instead of i386
then for a very long time, RH wasn't providing any package besides the one included in the RH releases. there was some guy providing RH UNOFFICIAL packages for the KDE team (they were even compiled against cups, whereas till 7.3 RH used only lpd). It was the first time with RH7.2/KDE2.2.2 when things were handled more or less correctly (except that Bero did a bad packaging -that qt2.3.2 thing-, mostly because he was in a hurry i think)

RedHat has always had a bad attitude towards KDE. they focus on GNOME (a bit) and server-side (a lot). Bero is doing alone packaging for KDE, and i agree it's a far too difficult work. After that, for sure, RH's CEO can go bashing "Linux isn't ready for the desktop" everywhere....

As for making money, RedHat is the most profitable Linux distro as i know.
So i ask them in a very polite way to handle KDE correctly ;-))

Ok, thanks for the info loopkin. I assumed it was RedHat providing those packages, but now I recall it was actually Bero doing it in his spare time. I switched to KDE since 2.2, so I wasn't aware of the past histoy (I used to use twm and later Gnome).

As for RedHat's bashing of Linux on the desktop, I agree in what you say and I think THEY DON'T GET IT. if you don't have a grip on the desktop market you will lose it on the servers market. That's how M$ got heavily into the servers market, with this horrid NT OS. Sys Adms had to reboot daily (!) to keep them running. But they still used it "because it was M$". And M$ got the their name recognized because of desktop dominance (plus FUD plus monopolic behavior plus marketting).

Why they don't change it's status and why you dont keep community informed about the progress.

Pls don't make the mistake of loosing the community by not informing what's going on and what is current progress.

Also something about the dot, the news-per-day are too small, for dot readers i just want to remember that when freekde.org was live there were 2-3 times more news per day and that was fine.

Don't forget that in opensource the most important thing is the community (not only contributors, developers, designers, translators but end-users, administrators, promoters, middle and small business too), and the community dies without fresh news, forums, lists, updates, releases, etc (any suggestions???).

Anyway kde community is very strong and hard, i personally visit kde.org and the dot every earth day and promote it! But if we want to bring more users and contributors to community we should more active. (Example: look at the other camp and see that they have news almost every day no matter that the news are bull-shits and that their progress is zero compared to the progres of kde (if some one cannot guess the other camp it's http://www.gnome.org )

No, it is basically the same team with some new help, and we now coordinate our efforts more closely on the kc-kde mailinglist and use CVS to put our summaries so we can fix typos and markup stuff in a joined effort, putting less stress on the head editor who still sends the final version in for publishment.

> But if we want to bring more users and contributors to community we should
> more active.

Do you mean more news activity ?

> Example: look at the other camp [.. gnome.. ] and see that they have news
> almost every day no matter that the news are bull-shits and that their
> progress is zero compared to the progres of kde

In my opinion this (bull-shit news) is a serious reason just to mention real progress on this news site. I am reading a lot here, but i would consider it is a waste of time of many surfers if dot.kde.org report about every little progress in an application. In this in 2 ways

1. resources needed to write the news here
2. all the time wasted from thousands of surfers by reading minor
important news (did you ever caught yourself by reading non-informative
comments (for example browsing slashdot.org) and wondered about yourself
why you are reading such a bull??it)

Let´s go coding / learn to code.

As said before Thanks for KDE guys.

P.S.
Desperatly waiting for kde 3.x debs so that i can switch over to debian (or should i switch to gentoo www.gentoo.org (sounds difficult and time consuming for a linux newbee - compile nearly everything from source on a Celereon 433 and slow internet connection)

Using MDK8.2 here and tried the rpm's, but even after a clean install KDE is messed up... it installs in different places, it saves some settings in you ~/.kde and some in ~/.kde3, my 'root'-user's panel was completely empty except for a taskbar, the K-menu and kalarm or something. It just copied the skeleton all wrong...

I'd rather use my cvs version compiled with 3.1 that works flawlessly.
After having updated kde regularly from cooker (it worked) I decided now to switch to 3.0.1.... what a mess:

*As you said, the installation was completely disorganized.
*I had to replace both kde and kde3.0 installations.
*It had dependencies with old packages (for.ex. librpm), so it wasn't possible to upgrade after having the newer libraries.

WHO provides this packages for Mandrake? They're not even in the cooker section. Are they official packages?????

./configure --with-qt-dir=/usr/lib/qt3 --prefix=/usr/local/kde3.1
make
make install

where (/usr/lib/qt3) is the library where Mandrake installs qt3, and (/usr/local/kde3.1) is the place I usually install kde cvs.

Compile it in that order: first arts, then kdelibs, then kdebase. You can try it at this moment. After that install the other packages: the order should not be important.

PS: Usually the main packages have no problems for compiling, but some packages like koffice or kdemultimedia have big changes sometimes, and they don't compile instantly. They're usually not difficult to fix though, if you know some c. Good luck!

Yes, it is a little bit tricky! At first I've removed kde-2.2.2 and then an update to kde-3.0.0, that was all. Now my system works fine again. Ok, all my configurations now in .kde3, not .kde but I've copied the necassary files by hand to the new directory.

A good place to set it is startkde, assuming you want all users to have the same home directory - otherwise, it's kinda dependant on how your distro is setup - it would be a good idea to take that to their support channels, like those on irc.openprojects.net (#suse, #mandrake, etc). It's a question more of what you're doing before KDE is run than how it's running, so it's OS dependant.

Regardless, this is not the right forum for KDE support - try the various KDE mailing lists at lists.kde.org for your OS.