|
Bugzilla – Full Text Bug Listing |
| Summary: | upgrade KDE4 using stable repos has an internal conflict and can lead to breaking an installation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | Mark Van De Vyver <mvdv> |
| Component: | 3rd party software | Assignee: | E-mail List <opensuse-communityscreening> |
| Status: | VERIFIED WORKSFORME | QA Contact: | E-mail List <opensuse-communityscreening> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
YaST2 conflicts screenshot 1
YaST2 conflicts screen shot 2 YaST2 compiz conflicts screenshot yast2 dep resolver test case mentioned in Comment |
||
|
Description
Mark Van De Vyver
2009-04-24 13:00:03 UTC
Created attachment 288046 [details]
YaST2 conflicts screen shot 2
> KDE:/KDE4:/Factory:/Desktop/openSUSE_11.0/KDE4-BASIS.ymp
This URL doesn't fit into your bug report (Factory!=STABLE). Otherwise removed
kdebase4-workspace-plasmoids from pattern (and bumped it to 4.1), compiz problem can not be solved in single repository - best deinstall compiz. :-)
My apologies Stephen, I didn't scroll far enough down the openSUSE/KDE wiki page before copying the ymp link. Step 8. should refer to: http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.0/KDE4-BASIS.ymp It is definitely a Stable bug. Did you try again before reopening this bug report? All that has changed is that it is now a compiz conflict that wants to uninstall, deinstall, downgrade to KDE 4.0.4 Since this is likely to be the way KDE3 and KDE 4.0 users will upgrade, it seems serious. See attached screenshot. Created attachment 288236 [details]
YaST2 compiz conflicts screenshot
Created attachment 288525 [details]
yast2 dep resolver test case mentioned in Comment
Bug was closed prematurely, only the first of two reported conflicts was resolved.
Both conflicts result in similar behavior.
No reponse from Novell and I've moved on :) |