On 24 July 2011 16:15, Tejas Guruswamy wrote:

On 24/07/11 13:18, Günther J. Niederwimmer wrote:

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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 24 July 2011 16:51, Bruno Friedmann wrote:

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

Any news on planned way out of the KDE update problem that occured in Tumbleweed, that can be passed on via forum? Tumbleweed seems to have attracted some distro-hoppers who aren't (yet) developers, who say nice things like "just about the same versions as Fedora but much more stable". This seems like a good thing, long term and some timely statement would likely be appreciated rather than leaving it to speculation. There were some questions already yesterday. Regards Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org