667802 – kpackagekit update fails if some packages cannot be updated

Bug 667802 - kpackagekit update fails if some packages cannot be updated

Summary: kpackagekit update fails if some packages cannot be updated

Status:	RESOLVED DUPLICATE of bug 637764

Alias:	None

Product:	openSUSE 11.4
Classification:	openSUSE
Component:	KDE4 Applications (show other bugs)
Version:	Factory
Hardware:	x86-64 Other

Priority:	P5 - None Severity: Critical (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2011-01-28 00:20 UTC by Todd R
Modified:	2011-02-18 21:05 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Todd R 2011-01-28 00:20:50 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b10) Gecko/20110121 Firefox/4.0b10

With YaST, when doing an update where some of the packages have conflicts that prevent them from being updated, you are given options on how to deal with the conflict (including just not updating those packages).

However, when doing an update with the software management KCM module, you just get an error and the update fails.  There is no way to just update the packages you can. 

Further, and selections you set are lost after the update fails, making it harder to manually deselect the failed packages.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Will Stephenson 2011-02-18 21:05:45 UTC

This description matches the behaviour of the broken packagekit zypp backend.

*** This bug has been marked as a duplicate of bug 637764 ***