The issue is that K:D:F is being updated bit-by-bit to 4.7 RC2, and
repository publishing is disabled during this time to avoid presenting an
inconsistent set of packages to users. However Tumbleweed also links in to
K:D:F packages, but noone disabled the publish flag for it. So Tumbleweed
currently has an inconsistent set of packages.

Which Packman apparently is building against to... it is having knock
on consequences at the weekend when Packman packagers tend to find
time to update things..

Surely Tumbleweed is meant to only acquire Factory packages deemed
"stable", it's not that the packages are inconsistent during the
update to 4.7 RC2, but that Tumblweed is picking up the Factory
updates at all. Even if KDE Factory was ready & consistent,
upgrading KDE 4.6 to 4.7 RC2 would seem against Tumblweed policy.

Rob

Tumbleweed is normally linked to the stable KR46
But you know what : sometimes shit happens.

Packagers are already looking why some package like kde4-runtime try to have a
4.6.95 (kde4.7rc2) version