I can access this rpm with every http program, but Yast think it doesn't exist. Fu** up. This makes me very angry. One reason is Yast and the other reason is that you think I spread lies.
One more reasons are people who doesn't find any bugs in Suse 10.2 and heavily use 10.2. I can't imagine this. I think they only use heavily Firefox, Konqui and one Mailer. Ok, if I only use these programs, then I don't find bugs too for hours/days/months/years... ;)

All in all, Suse 10.2 shouldn't release a distro because they can sell the boxed version BEFORE x-mas.

Thx & Greets,

anonymous "troll" (if you think I'm a troll, I'm a troll. but I don't lie)

And now? This doesn't help me at the time, Yast wants to download packages.

> Please report this to opensuse and/or use another softwareserver.

And at the next day, I report the next mirror which isn't temporarly avalaible? ;)

I think Suse know this problem, because the software download problem exist since the 1st implementation in Suse. And it is a really common and primitive administration task.
If they have a good error handling in Yast, Yast should try the next mirror and don't stop installing software.

I'm getting hopeless and angry if I want to install software, but Yast gambles about installing or refusing the package.

>>And now? This doesn't help me at the time, Yast wants to download packages.

is that a problem?

>>And at the next day, I report the next mirror which isn't temporarly avalaible? ;)

Yup, the more we bug novell with non working mirrors, the more they can do about it ;)

>>I think Suse know this problem, because the software download problem exist since the 1st implementation in Suse.

I'm not aware of that, never had any problems with yast sources.
software management nog is completely different now then it was in the beginning: now suse looks for mirrors itself, while before it would only use the repository that you have added in yast.
So they are working on it ;)

I'm sorry but you were not being very tolerant. You simply dismissed the distro with an anonymous post saying "it's buggy". Possibly the most undescriptive statement around.

> If I say it's buggy it IS buggy for me.

Once again, a useless statement. Since it's not buggy for me, it's not a buggy release; easy. Your screenshot there also doesn't give us enough information, and I can't reproduce it at all. If you're just ranting, then fine; but if you actually think it's a bug please feel free to open up a bug report though and then we can get to the bottom of it.

> One more reasons are people who doesn't find any bugs in Suse 10.2 and heavily use 10.2. I can't imagine this.

You mentioned one bug that we (and at least I) can't reproduce. Yes, I see the bugs overflowing now.

> All in all, Suse 10.2 shouldn't release a distro because they can sell the boxed version BEFORE x-mas.

Err, yeah, because you know how many people get openSUSE boxes for Christmas.. It was released when it was because of a release schedule that was set very many months before.

This whole discussion about posting distribution news on the dot isn't going anywhere. And being an important one, I hope that the KDE editors read this post.

It is I think really necessary to implement criteria for a distribution post to be accepted. This "if someone writes an article it will be accepted" won't work. We could soon have voluntaries writing release articles about everyone's pet favourite distribution spamming the dot.

So a distribution release news article should be posted if and only if it has some news related to KDE, not just because it includes KDE 3.5.x.

Taking that into account, Kubuntu's and openSUSE's news did make sense, while Fedora's was completely unwarranted. openSUSE and Kubuntu are, in that order, the distributions that are doing more KDE related work than any other. Actually employing KDE developers is among the best things you can do to support KDE. That said, not every openSUSE or Kubuntu release is interesting KDE-wise. SUSE's 9.x releases would maybe have been less news-noteworthy, KDE wise, independently of being good releases and a good distribution or not. But the last releases where related in a big way. Kubuntu has deployed a new KDE-based debian packet manager (Adept), it ships KControl's alternative System settings, including the new KControl modules from guidance, it has developed and shipped qt4 utilities like Kubuntu Device Database, the installer, etc. openSUSE, apart from the long history of supporting KDE, and its configuration utilities based on qt (YAST), has lately developed important KDE technologies or KDE frontends to new technologies like KNetworkmanager or Kerry, and this last release has an extremely important and relevant to KDE new item: Kickoff a replacement for KMenu which could influence KDE4's design, something that doesn't happen often. Those are interesting, KDE related news, worthy of being posted on the dot. Fedora's and any "distribution X released with KDE 3.5.x" are just metoos, kindergarten posts that spamm the dot.

I think the problem with Kubuntu's and openSUSE's announcements where not properly stressing AND explaining the KDE related points.

And Fedora has a very strong kde community, which justifies news about fedora on the Dot.

And besides that, I think it is important to spread news on the dot about who's shipping KDE with their product. That way, we can show how popular KDE is.
If we keep silent about the spreading of KDE among distributions, and other desktop environments don't, people tend to think that we are losing momentum and might choose another product then KDE.

nearly EVERY distribution ships with KDE (some as default, some, like Fedora not). That doesn't justify turning KDE.news into a bad version of distro watch. What exactly learns someone using KDE and Fedora by reading that piece of news? don't you think they know already their favourite distribution released a new version? And what exactly learn the other dot readers? That Fedora released a new version like every 6 months? and ships with the latest stable KDE? They already know that.

True, but still we get threads on the dot about 'kde is losing momentum'
We should alway continue to tell the audience that kde is popular, that kde ships with every distro on the market.

look for example at microsoft: every advertisement about computer systems reads 'vendor X recommends Windows XP'. That looks like a completely bogus recommendation, since every system that vendor X sells comes with XP as only OS installed, and allmost everyone using computers never heard of anything else but Windows..

>>What exactly learns someone using KDE and Fedora by reading that piece of news?
Nothing, but the news is not solely meant for fedora users.

>>And what exactly learn the other dot readers?
That Fedora ships KDE as well.

Looks like a bogus message, but to a lot of people, it is not.
We need to keep reminding the audience that they can choose from a variety of inux distributions if they want a kde desktop
If we don't, than we will loose momentum.
Just like microsoft keeps reminding their users that they should use Windows, even if those users were never aware that there was something besides Windows available.

>>They already know that.

Then we could just stop publishing any news on the dot, because the audience already knows about everything happening around KDE.

But don't get suprised if KDE starts loosing momenten as soon as we stop publishing news about kde and related projects..

Yes but that doesn't mean anything (is he doing it in his free time, for example?).

When the next Red Hat (or Fedora) release ships, you don't say, "mornfall is employed by Red Hat so they support KDE, it deserves to be announced on the dot"
What matters is "does this release have anything at all particular that involves KDE apart from shipping with it?"

Is Mandriva still contribution to KDE? they used to be one of the bigger sponsors (and have invested a lot when they could not affod it).

BTW. I agree on honesty about buggyness. I have installed Kubuntu now in 2 versions on 2 computers, and it works as a dream until something goes wrong with the wireless connection, and the SU system goes completely wrong. This is very bad as you cannot login as root. Searching on the web gives no help: many people suffer from the same problem, nobody really helps, only temporary workarounds. When I reboot 2 times, sometimes the problem is gone. The other workarounds don't even work.

Concluding: the distribution is in my opinion too buggy to show to release, but all reviews are raving.

Yes I am not saying that SUSE and Kubuntu are the only distributions supporting KDE. Madriva does too. But as I said that doesn't automatically make such a post on the dot meaningful.
If Madriva's next release does something new with or on top of KDE that not the other 100 distributions do, it will also be interesting to read about it on the dot.

I publish distro news for important KDE distributions where someone submits a story that is about the KDE part of the distribution. This is what you seem to be describing above and this openSuSE story and the recent Kubuntu one both fall into this description. The Fedora story doesn't, and shouldn't have been published in my opinion, but other dot editors have their own preferences.

Yes we agree. As I said, I think it was a communication problem. Not everyone will find it extremely interesting that Kubuntu or openSUSE ship a new version of the distribution with KDE3.5.x. But how about explaining those new nifty qt4 apps or frontends that Kubuntu now has? like the laptop suspend applet, the Device database initiative and the new Guidance modules with a System settings redesign? And what's new in Kerry and KNetworkmanager (which distributions like Kubuntu are evaluating as default for the next version), and some more Kickoff news (as it was already presented in an older dot article, I think).

not all derivations are bad. i can't speak about kickoff, haven't yet tried it - but suse has been shipping for a while kde with kicker menu search. it's awesome, it's useful - and from my viewpoint, should have been in default kde installations a long time ago.

also, such derivations allow for some real life testbeds, so if a feature is demed good enough, i guess it can be implemented in main kde :)