From time to time I run a "LC_ALL=C zypper -v se -s | fgrep '(System Packages)'" and/or a "zypper -v dup" to know if there is any problem in my installation. But I should not need to. And I'm pretty sure that, even if KDE now "works" for jayambe40, if he executes
http://bugzilla.novell.com/show_bug.cgi?id=492256 User cmorve69@yahoo.es added comment http://bugzilla.novell.com/show_bug.cgi?id=492256#c13 --- Comment #13 from Cristian Morales Vega <cmorve69@yahoo.es> 2009-04-08 08:05:29 MDT --- I don't know too much about Qt. But it's my understanding that all the 4.x series are ABI compatible. So... yes, it would look like an ABI breakage that would be a bug to be fixed. But since we are building and rebuilding so much to not have to worry about ABI breakages... kde-maintainers will decide. In any case if we are going to suppose the user is using the same Qt version the package was built with some changes are needed. If my memory doesn't fails the KDE:KDE4:Factory:Desktop project: - At some point was configured to build against KDE:Qt. - At some point it had links or aggregates to the packages from KDE:Qt. - Right now uses the official Qt packages. So, "ZYpp services" are needed so the user can keep in sync. But even with ZYpp services once the user has updated to the qt packages from "KDE:Qt" ZYpp will not downgrade to the official Qt packages. So the user never is going to have the correct qt packages if he doesn't selects them manually. the "LC_ALL=C zypper -v se -s | fgrep '(System Packages)'" command some inconsistencies in his installation would be shown. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.