Bug 327679

Summary:	software manager: "autocheck" state is not remembered
Product:	[openSUSE] openSUSE 10.3	Reporter:	macias - <bluedzins>
Component:	YaST2	Assignee:	Stefan Hundhammer <shundhammer>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None
Version:	RC 1
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	yast logs

Description macias - 2007-09-24 09:14:59 UTC

In opensuse 10.2 I didn't have problems with autocheck -- I have it turned off.

In 10.3 by default it is turned on, so I turned off, I installed some packages, "want to install more?" -> yes, autocheck is turned on.

I turned it off again, I installed another package, I answered this time "no" (so I quit SM), I ran it again, autocheck is turned on again.

( Since it worked well in 10.2 it is a regression, so instead of a wish, I am setting severity to minor )

Comment 1 Matej Horvath 2007-09-25 16:32:52 UTC

Reproduced.

Comment 2 Matej Horvath 2007-09-25 16:33:25 UTC

Created attachment 174668 [details]
yast logs

Comment 3 Stefan Hundhammer 2007-09-26 09:38:28 UTC


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

Comment 4 macias - 2007-09-26 09:50:35 UTC

Stefan, I am reopening because by all means it is not a duplicate.

The other report is a WISH -- it is about remembering column size. Yast didn't have such feature before.

This report is a BUG -- it is about working with yast and auto-checking all dependent packages. Yast _had_ such feature, it worked, now it does _not_. It is a regression.

Comment 5 Stefan Hundhammer 2007-09-26 12:52:40 UTC

It's a SETTING.

Thank you for wasting my time with this for the second time today. Obviously even without reading what the others were all about. We would work a lot more efficiently if we didn't have our every move second-guessed by people who think they know better.

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

Comment 6 macias - 2007-09-26 13:20:36 UTC

Sorry Stefan, but what severity is of the other report then? Wish or bug?

The other report is about __ENHANCING__ features.

I reported feature that __WAS WORKING__ fine and it is __BROKEN__ now.



And about other comments -- I've read them now because I always assume the duplicate is a duplicate really. It would be better to change summary of the other report to "common divider" -- I see you are closing each report twice really, maybe it is all fault of the reporters, but maybe it is unclear summary of the original report?

Anyway, once again, two reports asking for implementing feature X and other saying the implemented feature X does not work, are two distinct reports, not duplicates.

Comment 7 Stefan Hundhammer 2007-09-26 14:18:40 UTC

It's not "broken", it's changed behaviour. Intentionally changed behaviour. Changed upon request. Autocheck is on by default now.

Comment 8 macias - 2007-09-26 14:41:30 UTC

My humble apologies, Stefan!