| Summary: |
Buildservice: kdebase4-workspace-branding-openSUSE-11.0-37.2 conflicts with kdebase4-workspace-branding |
| Product: |
[openSUSE] openSUSE 10.3
|
Reporter: |
Richard Bos <richard.bos> |
| Component: |
KDE | Assignee: |
E-mail List <kde-maintainers> |
| Status: |
RESOLVED
DUPLICATE
|
QA Contact: |
E-mail List <qa-bugs> |
| Severity: |
Normal
|
|
|
| Priority: |
P5 - None
|
|
|
| Version: |
Final | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
i586 | |
|
| OS: |
Linux | |
|
| Whiteboard: |
|
|
Found By:
|
---
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
Since Friday 11 April 2008 I get the following error message when trying to upgrade KDE with smart: # smart upgrade --yes ...... kdebase4-workspace-branding-openSUSE-11.0-37.2 conflicts with kdebase4-workspace-branding It is possible to get the packages installed with zypper, but normally I use smart. It concerns the following packages: med103:~ # rpm -qa | grep workspace kdebase4-workspace-branding-openSUSE-11.0-37.1 kdebase4-workspace-plasmoids-4.0.1-39.4 kdebase4-workspace-4.0.3-38.1 med103:~ # smart upgrade --dump 2>&1 | grep workspace kdebase4-workspace-4.0.3-38.2@i586 kdebase4-workspace-branding-openSUSE-11.0-37.2@i586 kdebase4-workspace-plasmoids-4.0.1-39.5@i586 It's btw rpm that is failing (and not really smart): # rpm -Uvh kdebase4-workspace-branding-openSUSE-11.0-37.2.i586.rpm error: Failed dependencies: kdebase4-workspace-branding conflicts with kdebase4-workspace-branding-openSUSE-11.0-37.2.i586 The weird thing is this: # rpm -q kdebase4-workspace-branding package kdebase4-workspace-branding is not installed # rpm -qp --conflicts kdebase4-workspace-branding-openSUSE-11.0-37.2.i586.rpm kdebase4-workspace-branding # rpm -qp --requires kdebase4-workspace-branding-openSUSE-11.0-37.2.i586.rpm kdebase4-workspace plasma-theme-aya .... # rpm -q --requires kdebase4-workspace | grep work kdebase4-workspace-branding = 11.0 libQtNetwork.so.4 libkworkspace.so.4 Looks like a circular conflict - require problem in the packages mentioned above. Although these are packages delivered by the build service and as such these are perhaps not covered by this bugzilla, I don't know where to turn to otherwise. Hopefully this dependency problem can be resolved?