253059 – YaST Online Update refuses to install updates (because of locked package)

Bug 253059 - YaST Online Update refuses to install updates (because of locked package)

Summary: YaST Online Update refuses to install updates (because of locked package)

Status:	RESOLVED DUPLICATE of bug 191810

Alias:	None

Product:	openSUSE 10.2
Classification:	openSUSE
Component:	libzypp (show other bugs)
Version:	Final
Hardware:	i686 Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Stefan Schubert
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-03-09 17:10 UTC by Tristan Miller
Modified:	2007-03-14 16:22 UTC (History)
CC List:	0 users

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

Attachments
YaST logs (1.97 MB, application/x-bzip2) 2007-03-09 17:22 UTC, Tristan Miller	Details
View All 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 Tristan Miller 2007-03-09 17:10:01 UTC

This bug report is split off from Bug 234539.

Reproducibility: Always

Steps to reproduce:
1. Run YaST
2. Select "Online Update"
3. YaST Online Update may indicate that there is a conflict due to a locked package.  If so, select "Unlock all resolvables".
3. YaST Online Update lists various updates to install.  Click OK.
4. A progress window appears.  After a few seconds, the message "Installation
complete" appears.  However, none of the updates actually get installed.  If
you run YaST Online Update again, it offers to install the same set of updates.

Comment 1 Tristan Miller 2007-03-09 17:22:48 UTC

Created attachment 123570 [details]
YaST logs

Comment 2 Jiří Suchomel 2007-03-12 07:52:16 UTC

Doesn't look like a problem in ycp part.

Comment 3 Stefan Schubert 2007-03-14 16:22:27 UTC

Thank you for the logs;-)
Patches will be updated. That does not work correctly. Has already been fixed.

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