Bug 290986

Summary:	YaST erroneous reports two versions of acpid being installed
Product:	[openSUSE] openSUSE 10.3	Reporter:	Casual J. Programmer <casualprogrammer>
Component:	YaST2	Assignee:	Stefan Schubert <schubi>
Status:	RESOLVED INVALID	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	casualprogrammer
Version:	Alpha 5plus
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 10.3
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 Logs

Description Casual J. Programmer 2007-07-11 07:02:22 UTC

On updating acpid with YaST sw_single the old version does not get removed, instead both are reported, the old one as having updates available.

Selecting the newer (1.0.6-2) as "keep" and the previous (1.0.4-82) as "delete" results in an error:


---
2007-07-11 08:42:58 acpid-1.0.4-82.i586 remove failed
rpm output:
error: package acpid-1.0.4-82.i586 is not installed

2007-07-11 08:44:15 man-pages-2.61-2.noarch.rpm installed ok
2007-07-11 08:44:23 arpwatch-ethercodes-2007.7.10-2.noarch.rpm installed ok
2007-07-11 08:54:24 acpid-1.0.4-82.i586 remove failed
rpm output:
error: package acpid-1.0.4-82.i586 is not installed

Selecting "All in this list/Update if newer version available" will mark both entries for update.

Executing the update will add another instance of acpid 1.0.6-2

Comment 1 Casual J. Programmer 2007-07-11 07:03:53 UTC

Created attachment 150666 [details]
YaST2 Logs

Comment 2 Ladislav Slezák 2007-07-19 06:59:38 UTC

Stefan, could you check why was the package installed twice instead of update?

Comment 3 Stefan Schubert 2007-07-19 07:12:41 UTC

I cannot see very much in the "normal" YaST logfiles. Could you please reproduce it and generate a testcase for that case ?
http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F

Comment 4 Casual J. Programmer 2007-07-19 11:52:35 UTC

This has finally resolved itself after consistently hitting retry umpteen times. So I am afraid, until something similar shows up again, we are left with the "normal" yast2 logs, sorry.

Comment 5 Stefan Schubert 2007-07-19 11:58:47 UTC

I cannot do very much without the logfiles. Feel free to reopen the bug if you
can provide the testcase.