466569 – software management: no final reports on error

Bug 466569 - software management: no final reports on error

Summary: software management: no final reports on error

Status:	RESOLVED DUPLICATE of bug 431854

Alias:	None

Product:	openSUSE 11.1
Classification:	openSUSE
Component:	YaST2 (show other bugs)
Version:	Final
Hardware:	x86-64 Other

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	Ladislav Slezák
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2009-01-15 19:48 UTC by macias -
Modified:	2009-01-19 15:08 UTC (History)
CC List:	0 users

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

Attachments
y2logs 32-bit (111 bytes, application/x-tgz) 2009-01-19 13:53 UTC, macias -	Details
y2logs 64-bit (111 bytes, application/x-tgz) 2009-01-19 13:56 UTC, macias -	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 macias - 2009-01-15 19:48:05 UTC

software management: no final reports on error

I was told (opensuse team) that SM does not close on finishing install if there are any errors. Well, SM does not behave like that.

Some package was unavailable (network down), I skipped it, and when installing was finished, no summary with errors, SM quitted "as always".

Comment 1 Cyril Hrubis 2009-01-18 17:58:29 UTC

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!

Comment 2 macias - 2009-01-19 13:53:50 UTC

Created attachment 266005 [details]
y2logs 32-bit

Comment 3 macias - 2009-01-19 13:56:29 UTC

Created attachment 266006 [details]
y2logs 64-bit

Ok, my fault, I am really sorry -- I didn't wrote down which log is which, i.e. on which computer this error occurred. I am very sorry for that.

So I attached both logs.

Comment 4 macias - 2009-01-19 13:58:58 UTC

Comment 5 Ladislav Slezák 2009-01-19 15:08:33 UTC

Duplicate of #431854

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