Bug 570357

Summary:	update applet does not honor package locks
Product:	[openSUSE] openSUSE 11.2	Reporter:	Thomas Schmidt <tschmidt>
Component:	libzypp	Assignee:	Scott Reeves <sreeves>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	83097markcynt, qantas94heavy, tgoettlicher
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	zypper log

Description Thomas Schmidt 2010-01-13 15:33:11 UTC

Created attachment 336423 [details]
zypper log

I currently have installed timezone-2009p-1.1.1.i586 and there is a timezone update in the update repo: timezone-2009u-1768.noarch

I try to lock the package, so that the update applet ignores it: 
> sudo zypper al timezone

Doing: 
> sudo zypper up -t patch
Problem: patch:timezone-2009u-1768.noarch conflicts with timezone.i586 < 2009u-0.1.1 provided by timezone-2009p-1.1.1.i586
 Solution 1: do not keep timezone-2009p-1.1.1.i586 installed
 Solution 2: do not install patch:timezone-2009u-1768.noarch

Choose from above solutions by number or cancel [1/2/c] (c):

gives this conflict, which the updater applet cannot handle, it just displays the first line of the error message. I would expect that the updater ignores locked packages. 

This is related to feature request #308522

Comment 1 Jan Kupec 2010-01-13 16:04:57 UTC

Yes, this is known since 10.3, it needs a fix in zypper (bug 420606). But regarding the updater applet, are you using the zypp backend or packagekit backend? If the latter, this will need fixing in the packagekit's zypp backend.

Comment 2 Thomas Schmidt 2010-01-13 16:18:53 UTC

I'm using packagekit

Comment 3 Jan Kupec 2010-01-14 13:12:10 UTC

Scott, can you please take care of this? Just check the resolvable's ResStatus::isLocked(), or Selectable::locked().

Comment 4 Karl Cheng 2017-08-12 05:33:21 UTC

Seems to be the same issue with KPackageKit.

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