That’s exactly what I did. This is not Tumbleweed specific. Happened before. What worries me, is that Tumbleweed is supposed to have “stable” packages, where serving *RC packages is more of a factory idea.
One of the habits I developped (probably not good in the eyes of some), is to check the actual content of repos and compare x86 vs x86_64 for example.
My 2 cents: just give it a couple of days, then try again.
Worried me to, got this answer on the factory list Re: [opensuse-factory] Tubleweed - KDE
Can’t find an announcement of this KDE repo change on Factory, just that forum post announcing it, so hardly surprising noone checked Tumbleweed.
There’s an impedance mismatch, there used to be something like KDE4:/stable & /latest, rather than fixing version numbers.
Rob
I noticed the same problem today and i did stop making updates; Apper says that i have 8 updates i suspect after the cleanup or wrong packages that i will have plenty from Tumbleweed.
This does not mean Factory. the K:D:F from the mailinglist refers to the KDE:Distro:Factory repo. That one is known to switch to the KDE RC’s. As long as a KDE version is in beta stage, it appears in KDE:UNSTABLE, the release candidates make it to the mentioned KDE:Distro:Factory repo. AFAICS the 32bit Tumbleweed KDE packages are complete, it seems it’s just the 64bit packages. I’ll do a more thorough checking and get back here.
Edit: Did check, I was wrong assuming this would be a 64bit issue. The “mix” is there for 32bit as well.
What’s a geek to do without a button to push? Watch TV? Cook?
Put this up full screen and indulge yourself:
http://thumbnails33.imagebam.com/14204/60210c142032304.jpg](ImageBam)
Or ask the Mrs if she has any suggestions. If your track record is good, you may be in luck 
Problem is that IMHO Tumbleweed is supposed to be the “not-so-broken factory”. At least I’d like to use it without manually crosschecking all packages in all repositories, and scanning all forums for potential problems before doing an update (which are available several times a week). “Waiting until things settle down” sounds good, but how do I know when things settle down (and when they are beginning to get unsettled)?
So there something went wrong in the build system leading to the breakage of a major desktop environment, which is a problem that should be addressed. (The masses of different KDE repositories don’t make it any easier for the maintainers, I guess. Something seems to have creeped in…)
but how do I know when things settle down (and when they are beginning to get unsettled)?
Keep an ear to the ground.
If you plan to use non-standard repos, then expect to have to work at it.
Though I would say this: It seems to me that ‘Tumbleweed’ as described here:
Portal:Tumbleweed - openSUSE
Is a little misleading. It implies stability and then suggests we can contribute to it’s ‘Testing’. Personally, I suggest the project managers revise the statements made there, in order that users are aware of potential pitfalls of the testing process.
The Factory mail list is used for Tumbleweed issues and as the plan was to migrate Factory to 4.7 RC2 information there would have been not only appropriate, but had more chance of being read by those affected or who could have avoided unwanted repo updates…
For some reason, Tumbleweed KDE was linked to that KDE:Distro:Factory repo, not a 4.6 one, someone explained “temporarily”. Package developers push out things for Tumbleweed, when they deem them as “stable”; if a plan was there to upgrade Tumbleweed to RC2 it ought to have been discussed. If Tumbleweed was meant to track KDE4 Stable (ie remain at 4.6) then action appears to have been necessary to switch to the KDE 4.6 repo.
Announcing just on forum on a Friday in a section I cannot even find now (uinless I do history search or re-read posts here) and on the KDE mail list, about a change of widely used packages like KDE desktop seems not to be effective communication. Like Bernhard Wiedeman said… “sh*t happens”.
I think the problem is basically that Tumbleweed was not using packages OBS linked to a KDE4 “Stable” repo, but the KDE:Distro:Factory repo, which is being upgraded to RC2. It was explained that a “publish” attribute was taken off Factory, hiding the updates, but left on in Tumbleweed. Someone simply forgot or didn’t know action was necessary to smoothly make the change. The impedance mistmatch, is that Tumbleweed apparently could not just track a KDE4 Stable repo, for some reason; so when SuSE KDE 4.7 is ready for prime time, that repo would be updated in a planned way, with distribution to Tumbleweed expected after an update to KDE4:stable was deemed Tumbleweed worthy.
I agree that Tumbleweed is not meant to require all the cross-checking & scan for update problems. The not so broken factory is however supposed to be “factory-tested”, with Tumbleweed intended to be a useful rolling relelase for openSUSE desktop, with fresh software deemed “stable” by the developers.
Mistakes are inevitable however, that does not mean we should not recognise them and try to avoid them in future; to not try to improve things is actually against the Aims of openSUSE.
Wasn’t that page written around the launch of Tumblweed? Until this KDE 4.7 rc2 debacle, Tumbleweed has been by far the best version of openSUSE I’ve used, with most problems minor & rapidly fixed on feedback. Actually beacause I used zypper up, the few 4.6.95 packages I’ve picked up don’t seem to have destabilised my box.
The project list should probably discuss the future status of Tumbleweed, it seems to me that Tumbleweed using same Vendor as other openSUSE repos, and being a Full openSUSE release version, like 11.3, 11.4 & Factory would help (means Packman (and other repo) addition work same as in 11.3 or 11.4); though for comfortable rolling, I think a “Stumbleweed” - Solid Tumbleweed, with less churn and package updates filtered through Tumbleweed first, adding a buffer between the instability & churn of the bleeding edge; would likely become in time more popular than the traditional version based model - just like Debian Sid “unstable” is more popular than “stable”.
I switched to Tumbleweed on my Gnome 3 install
Added the TW repo + TW Gnome + PackmanTW
Switched on TW, then Gnome, then Packman
Handled a couple of errors
1.8GB later it’s beautiful
I don’t really care about a beautiful Gnome install 
. Is it known what the solution for the KDE situation will be? Will there be a switch to 4.7RC or will there be a downgrade of 4.6.95 to 4.6.5 for Tumbleweed? I don’t really know the current policy concerning KDE.
Answers to such questions would best be answered in the IRC or ML
This silence has been deafening on the mailing lists…
I would expect, a zypper dup downgrade of 4.6.95 packages back to 4.6 (or individual package downgrade by selection if you just did a zypper up), with in not distant future an upgrade to a KDE 4.7 release. The package downgrades, haven’t actually left ppl with totally unusuable systems have they?
Mine was completely usable (don’t know about other ppl). Maybe that’s why there is silence about it.
(even so I retrieved a backup and now use that, waiting for zypper to calm down)
I suspect that the team is working to solve this issue because this morning after 83 updates my KDE 4.6 was downgraded to release 7 instead of 8 that i use to have yesterday.
After the updates i still have this 2 problems:
Problem: nothing provides kdebase4-runtime >= 4.6.95 needed by k3b-codecs-2.0.2-8.pm.13.10.i586
Problem: nothing provides kdebase4-runtime >= 4.6.95 needed by kffmpegthumbnailer-1.1.0-1.pm.1.3.i586
I had to keep the old/obsolete package for k3b
I just wonder why it’s quoting 32 bit packages on your _64 system (as listed in your sig)
I dont know, i just applied the "do not modify" option in yast and now when i run zypper dup the problems dont appear anymore.
Latest news on Factory list, is that they’re building “sorted” Tumbleweed packages now, and hopefully “it’s all fixed”.
So just a little more patience required, this “glitch” hasn’t actually seemed to break anything seriously, so even if it’s not hit your mirror by the time you read this, it ought not be too long.
That`s good news robopensuse; for me the “glitch” as you called, did not break my system just forced me to use older versions of packages/programs.
