https://bugzilla.novell.com/show_bug.cgi?id=285482

Steffen Winterfeldt snwint@novell.com changed:

What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |schubi@novell.com

https://bugzilla.novell.com/show_bug.cgi?id=285482#c2

--- Comment #2 from Stefan Hundhammer sh@novell.com 2007-06-20 11:44:13 MST --- (In reply to comment #1 from Karl Eichwalder)

I'm wondering whether Check/Autocheck in the yast (qt) dialog of the "Software Management" dialog is meant to accomplish the same job or what a the subtle differences.

That's something different. The normal check/autocheck check the currently pending transactions, i.e., those packages that are marked for installation/deletion/update/whatever. It does not recompute all dependencies of packages that are already installed. It assumes that at some point in the past the dependencies of that system had been checked, and if there was some fault with it, the user had been informed and confirmed that he really wants it that way.

"Verify system" OTOH checks the complete system for consistency. It is not restricted to pending transactions.

https://bugzilla.novell.com/show_bug.cgi?id=285482

User schubi@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=285482#c4

Stefan Schubert schubi@novell.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |cmorve69@yahoo.es

--- Comment #4 from Stefan Schubert schubi@novell.com 2008-06-24 08:07:25 MDT --- *** Bug 402759 has been marked as a duplicate of this bug. ***

https://bugzilla.novell.com/show_bug.cgi?id=402759

https://bugzilla.novell.com/show_bug.cgi?id=285482

User cmorve69@yahoo.es added comment https://bugzilla.novell.com/show_bug.cgi?id=285482#c5

--- Comment #5 from Christian Morales Vega cmorve69@yahoo.es 2008-11-12 05:02:41 MST --- I don't have a 11.1 install to test, there is any improvement in this?

I don't know what "Fate 301178" is (should be at "https://features.opensuse.org/?rm=feature_show&id=301178%22?), but Karl explanation seems to mean that "verify installed package dependencies" somehow worked. When I reported bug #402759 (duplicate of this one) the situation looked different... seems that "verify installed package dependencies" just calls a funtion to show a window with a "System dependencies verify OK" message... but without making any real test!!

If right now the situation is the one explained at #402759 I would suggests that if it isn't fixed the option should be removed... a message saying everying is ok when there are problems (that you can really test and fix with "zypper verify") is just confusing and useless.

https://bugzilla.novell.com/show_bug.cgi?id=285482

User tgoettlicher@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=285482#c7

--- Comment #7 from Thomas Göttlicher tgoettlicher@novell.com 2009-03-12 09:46:12 MST --- As discussed face to face I'm going to use libzypp's setSystemVerification( bool yesno_r ) in the UI and add a menu entry called "System Verification Mode" to the "Options" menu.

https://bugzilla.novell.com/show_bug.cgi?id=285482

User gs@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=285482#c9

--- Comment #9 from Gabriele Mohr gs@novell.com 2009-03-16 07:56:21 MST --- The current behaviour of the ncurses package selector is like Michel's suggestion in comment #6. If changes are made because of system verify a popup with the list of changed packages appears automatically. I have talked to Thomas: the new implementation of Qt package selector works like this: there is a check box to switch verification mode on/off. Depending on this the system verify runs/doesn't run on every solver run. The packages which are changed due to the verify are included in the 'installation summary' and it's not obvious which packages are changed because of the system verify. I think the ncurses solution is more clear. The disadvantage of this approach is that after a 'verifySystem()' is called the system verification mode remains on for all solver runs. Maybe we can discuss again and find a solution with both approaches combined?

https://bugzilla.novell.com/show_bug.cgi?id=285482

User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=285482#c10

Michael Andres ma@novell.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ma@novell.com |

--- Comment #10 from Michael Andres ma@novell.com 2009-03-19 10:53:46 MST --- What we could do: Let it become a checkbox like in Qt now. But if the user switches systemverification mode AND autodependencysolving is on:

immediately Solve and automatically switch to and update the 'installation summary'

If autodependencysolving is off, do nothing special.

But Gabi is right, it should also become obvious, that this is a solver mode option, and not an action. Some help text review might be necessary.

Thinking it further, we may want to make even more solver options available in the ui in the future. So it may also become annoying, if changing an option in the menu immediately triggers some action. Esp. if there are solver problems.

So it might be a bad idea to 'immediately Solve and automatically switch...'.

Maybe we should just focus on making it obvious that this is a solver mode and properly document it in the help text.